iOS application launching

Product Considerations You Should Be Worried About Before You Launch Your iOS Mobile Application!

First of all, congratulations! You have successfully passed through the test that many other fail, developed an application that serves a purpose.

You have already started the countdown sequence for launching your iOS mobile application? Before you open the champagne, note the following 3 considerations you should start worrying about immediately:

Product considerations you should be worried about.

Are you ready for your last stop? Find out who controls product offering and fulfillment and set up a meeting. Almost certainly they will never have encountered the type of sales channel that iOS applications pass through and will require some adjustment on their part.

To begin with, you are going to have to explain to them that the concept of a Gold Master isn’t going to apply to the Apple Store. Actually there is no physical artifact that represents the version of the product you upload for sale into the App Store, because the only way to do that is from inside XCode.

Now, this can lead into some weird circumstances. For example you may be contractually required to ship a physical copy of the application to some customers. The question is  – What exactly is going to go on that CD? An Ad Hoc IPA file? Consumer won’t be able to use it because their devices are not in the provisioning profile.  What then? A copy  of IPA uploaded to the App Store? You can only install these by uploading them directly from the store. A README.TXT file? Trust my word, you would rather get this kind of conversation started early rather than negotiating around it in the final moment.

Another issue to discuss is how the final production build will be created and uploaded to the store. It needs (as already said) to be done from XCode which means a Mac and someone who knows how to drive it. They almost certainly do not want you upload it from your development machine. The accommodation we propose is to fire XCode on the build machine (that runs Hudson), point it at the directory with the sources from the last successful build and do an archive and upload from that.

And answer this – How the product is going to be priced?

Will it be given away and revenue made on server licences? Will there be volume licence arrangements available? Apple has recently added the ability to do custom volume deals with companies, so this may be an issue worth discussing with your fulfilment team. What kind of sales report would they want from iTunes Connect? Where do the checks from Apple need to go? Make sure that you are all on the same page regarding the logistics of selling via iTunes.