first iOS application and now you are ready to submit it to Apple’s App Store.
How do you go about this? You will want to ask yourself if your application is
ready for submission. I am sure that some of the following questions would have
come up on your mind at one point or another – Is submitting an application as
simple as sending Apple your application’s binary? Not quite. With this article,
I will provide you with a detailed guide to get your application submitted to
Apple’s App Store.
After you have worked for a long period on your
Introduction
Even though the App Store review process is a black
box for the most part, that doesn’t mean that you can’t prepare yourself and
your application for Apple’s review process. Apple provides guidelines to help
you stay within the sometimes invisible boundaries of what is and isn’t allowed
in the App Store.
box for the most part, that doesn’t mean that you can’t prepare yourself and
your application for Apple’s review process. Apple provides guidelines to help
you stay within the sometimes invisible boundaries of what is and isn’t allowed
in the App Store.
The first time you submit an application to the App
Store is exciting and nerve-racking at the same time. Even for experienced iOS
developers, submitting an application to the App Store is often a stressful
undertaking because it is something that most developers don’t do on a daily
basis.
Store is exciting and nerve-racking at the same time. Even for experienced iOS
developers, submitting an application to the App Store is often a stressful
undertaking because it is something that most developers don’t do on a daily
basis.
In this article, I am assuming that you will be a
registered iOS developer which means that you are enrolled in Apple’s iOS
Developer Program and are allowed to submit applications for publication in the
App Store. To submit an iOS application to the App Store, you need to be a
registered iOS developer. Red flag? Don’t worry. You can enroll in Apple’s iOS
Developer Program by visiting this link and clicking the Enroll Now button.
registered iOS developer which means that you are enrolled in Apple’s iOS
Developer Program and are allowed to submit applications for publication in the
App Store. To submit an iOS application to the App Store, you need to be a
registered iOS developer. Red flag? Don’t worry. You can enroll in Apple’s iOS
Developer Program by visiting this link and clicking the Enroll Now button.
1. Is
your application ready?
your application ready?
Step 1: Testing
An application is not actually ready when you have
written the last line of code or implemented the final feature of the
application’s specification. If you have not tested your application on one or
more physical devices or if you are yet to profile your application for memory
leaks and performance issues? Does your application crash from time to time?
The family of iOS devices has grown substantially over the past years and it is
important to test your application on as many iOS devices as you can lay your
hands on. Common issues include not optimizing an application for the iPhone
5’s 4″ screen or the iPad Mini’s 7.9″ screen.
written the last line of code or implemented the final feature of the
application’s specification. If you have not tested your application on one or
more physical devices or if you are yet to profile your application for memory
leaks and performance issues? Does your application crash from time to time?
The family of iOS devices has grown substantially over the past years and it is
important to test your application on as many iOS devices as you can lay your
hands on. Common issues include not optimizing an application for the iPhone
5’s 4″ screen or the iPad Mini’s 7.9″ screen.
Apple’s Review Process is not airtight, but it is
very capable of identifying problems that might affect your application’s user
experience. If your application crashes from time to time or it becomes slow
after ten minutes of use, then you have some work to do before submitting it to
the App Store. Even if Apple’s review team doesn’t spot the problem, your users
will. If the people using your application are not pleased, they will leave bad
reviews on the App Store, which may harm sales or inhibit downloads.
very capable of identifying problems that might affect your application’s user
experience. If your application crashes from time to time or it becomes slow
after ten minutes of use, then you have some work to do before submitting it to
the App Store. Even if Apple’s review team doesn’t spot the problem, your users
will. If the people using your application are not pleased, they will leave bad
reviews on the App Store, which may harm sales or inhibit downloads.
Step 2: Rules and Guidelines
As I mentioned earlier, Apple provides developers
with a number of documents that are a great help during the creation and
development process of your application. The documents that you must be aware
of are the iOS
Human Interface Guidelines and the App
Store Review Guidelines. Despite the
availability of these documents, only a few number of developers take the time
to browse them, not to talk of read them.
with a number of documents that are a great help during the creation and
development process of your application. The documents that you must be aware
of are the iOS
Human Interface Guidelines and the App
Store Review Guidelines. Despite the
availability of these documents, only a few number of developers take the time
to browse them, not to talk of read them.
Even if you don’t intend to read the iOS Human
Interface Guidelines or the App Store Review Guidelines, it is important to
know about some of the rules that they talk about. Take a look at the list
below to have an idea of what your application should and should not do.
Interface Guidelines or the App Store Review Guidelines, it is important to
know about some of the rules that they talk about. Take a look at the list
below to have an idea of what your application should and should not do.
Your application:
- doesn’t crash.
- shouldn’t use private
API’s. - shouldn’t replicate the
functionality of native applications. - should use In App
Purchase for in-app (financial) transactions. - shouldn’t use the camera
or microphone without the user’s knowledge. - only uses artwork that
you have the copyright of or you have permission to use.
Keep in mind that these guidelines were included in
the aforementioned documents. The majority of the rules and guidelines are
trivial, but some are not and you might even violate some of them
inadvertently. Let me give you an example. However, if some part of your
application’s user interface covered or obscured Google’s logo, your
application would get rejected. This rule seems trivial, but it is a rule that
is easily violated if you’re not careful. Even automated tests won’t cover you
in this case.
the aforementioned documents. The majority of the rules and guidelines are
trivial, but some are not and you might even violate some of them
inadvertently. Let me give you an example. However, if some part of your
application’s user interface covered or obscured Google’s logo, your
application would get rejected. This rule seems trivial, but it is a rule that
is easily violated if you’re not careful. Even automated tests won’t cover you
in this case.
2. Prerequisites
Before you can even start thinking about submitting
your application to the App Store, you should make sure that you have an App
ID, a valid distribution certificate, and a valid provisioning profile. Let me
show you what this entails.
your application to the App Store, you should make sure that you have an App
ID, a valid distribution certificate, and a valid provisioning profile. Let me
show you what this entails.
Step 1: App ID
Every application needs an App ID or application
identifier. There are two types of application identifiers, (1) an explicit App ID and (2) a wildcard App ID. A wildcard App ID can
be used for building and installing multiple applications. Despite the
convenience of a wildcard App ID, an explicit App ID is required if your application uses
iCloud or makes use of other iOS features, such as Game Center, Apple Push
Notifications, or In App Purchase.
identifier. There are two types of application identifiers, (1) an explicit App ID and (2) a wildcard App ID. A wildcard App ID can
be used for building and installing multiple applications. Despite the
convenience of a wildcard App ID, an explicit App ID is required if your application uses
iCloud or makes use of other iOS features, such as Game Center, Apple Push
Notifications, or In App Purchase.
Step 2: Distribution
Certificate
Certificate
To submit an application to the App Store, you need
to create an iOS provisioning profile for distribution. To create such a
provisioning profile, you first need to create a distribution certificate. The
process for creating a distribution certificate is very similar to creating a
development certificate. If you have tested your application on a physical
device, then you are probably already familiar with the creation of a
development certificate.
to create an iOS provisioning profile for distribution. To create such a
provisioning profile, you first need to create a distribution certificate. The
process for creating a distribution certificate is very similar to creating a
development certificate. If you have tested your application on a physical
device, then you are probably already familiar with the creation of a
development certificate.
Step 3: Provisioning Profile
Once you’ve created an App ID and a distribution
certificate, you can create an iOS provisioning profile for distributing your
application through the App Store. Keep in mind that you cannot use the same
provisioning profile that you use for ad hoc distribution. You need to make a
separate provisioning profile for App Store distribution. If you use a wildcard
App ID for your project, then you can use the same provisioning profile for
multiple applications.
certificate, you can create an iOS provisioning profile for distributing your
application through the App Store. Keep in mind that you cannot use the same
provisioning profile that you use for ad hoc distribution. You need to make a
separate provisioning profile for App Store distribution. If you use a wildcard
App ID for your project, then you can use the same provisioning profile for
multiple applications.
Step 4: Build Settings
With the App ID, distribution certificate, and
provisioning profile in place, it is time to configure your target’s build
settings in Xcode. This means selecting the target from the list of targets in
Xcode’s Project Navigator,
opening the Build Settings tab
at the top, and updating the settings in the Code Signing section to match the distribution provisioning
profile you created earlier.
provisioning profile in place, it is time to configure your target’s build
settings in Xcode. This means selecting the target from the list of targets in
Xcode’s Project Navigator,
opening the Build Settings tab
at the top, and updating the settings in the Code Signing section to match the distribution provisioning
profile you created earlier.
Step 5: Deployment Target
It is useful to write a few words about your
application’s deployment target. Each target in an Xcode project, has a
deployment target, which indicates the minimum version of the operating system
that the application can run on. It is up to you to set the deployment target,
but keep in mind that modifying the deployment target is not something you can
do without consequences once your application is in the App Store. If you
increase the deployment target for an update of your application, then users
who already purchased your application but don’t meet the new deployment
target, cannot run the update. It gets really problematic when a user downloads
an update through iTunes (not the device), replacing the previous version on
their computer, and then discovers that the new update doesn’t run on their
device.
application’s deployment target. Each target in an Xcode project, has a
deployment target, which indicates the minimum version of the operating system
that the application can run on. It is up to you to set the deployment target,
but keep in mind that modifying the deployment target is not something you can
do without consequences once your application is in the App Store. If you
increase the deployment target for an update of your application, then users
who already purchased your application but don’t meet the new deployment
target, cannot run the update. It gets really problematic when a user downloads
an update through iTunes (not the device), replacing the previous version on
their computer, and then discovers that the new update doesn’t run on their
device.
There are two very simple tips with regards to your
application’s deployment target. (1) Be very careful when you decide to
increase the deployment target of an existing application. Mention this in the
application’s release notes of the updates that precede the change and again in
the update that uses the new deployment target. If you warn your customers well
in advance, you have done all you can to prevent potential problems. (2) For
new applications, I almost always set the deployment target to the last major release,
iOS 6 at the time of writing. Because of the incredible adoption rate of new
iOS releases, there is no harm in doing this. Some people think that they miss
out on a large chunk of the market, but that is not true.
application’s deployment target. (1) Be very careful when you decide to
increase the deployment target of an existing application. Mention this in the
application’s release notes of the updates that precede the change and again in
the update that uses the new deployment target. If you warn your customers well
in advance, you have done all you can to prevent potential problems. (2) For
new applications, I almost always set the deployment target to the last major release,
iOS 6 at the time of writing. Because of the incredible adoption rate of new
iOS releases, there is no harm in doing this. Some people think that they miss
out on a large chunk of the market, but that is not true.
3. Assets
Step 1: Icons
You probably know that an application icon is a
vital component of every iOS application, but you need to make sure that your
application ships with the correct sizes of the artwork. Have a look at the
list below.
vital component of every iOS application, but you need to make sure that your
application ships with the correct sizes of the artwork. Have a look at the
list below.
- iTunes Artwork: 1024px x
1024px (required) - iPad/iPad Mini: 72px x
72px and 114px x
114px (required) - iPhone/iPod Touch: 57px x
57px and 114px x
114px (required) - Search Icon: 29px x
29px and 58px x
58px (optional) - Settings Application:
50px x 50px and 100px
x 100px (optional)
You also don’t need to include an application icon
for the iPad/iPad Mini device family if your application only targets the
iPhone/iPod Touch device family, and vice versa.
for the iPad/iPad Mini device family if your application only targets the
iPhone/iPod Touch device family, and vice versa.
Step 2: Screenshots
Each application can have up to five screenshots
and you must provide at least one. If you are developing a universal
application, then you need to provide separate screenshots for iPhone/iPod
Touch and iPad/iPad Mini. In addition, you can optionally include separate
screenshots for the 3.5″ and the 4″ screen sizes of the iPhone/iPod
Touch. This is quite a bit of work and you want to make sure that the
screenshots show your application from its best side.
and you must provide at least one. If you are developing a universal
application, then you need to provide separate screenshots for iPhone/iPod
Touch and iPad/iPad Mini. In addition, you can optionally include separate
screenshots for the 3.5″ and the 4″ screen sizes of the iPhone/iPod
Touch. This is quite a bit of work and you want to make sure that the
screenshots show your application from its best side.
It is important to spend some time thinking about
the screenshots. Your application’s screenshots are often the only thing that a
customer can use to decide whether she purchases or downloads your application
or not.
the screenshots. Your application’s screenshots are often the only thing that a
customer can use to decide whether she purchases or downloads your application
or not.
Step 3: Metadata
Before you submit your application, it is a good
idea to have your application’s metadata at hand. This includes (1) your
application’s name, (2) the version number, (3) the primary (and an optional
secondary) category, (4) a concise description, (5) keywords, and (6) a support
URL. If you are submitting an update, then you can also provide information for
the “What’s new in this Version” section.
idea to have your application’s metadata at hand. This includes (1) your
application’s name, (2) the version number, (3) the primary (and an optional
secondary) category, (4) a concise description, (5) keywords, and (6) a support
URL. If you are submitting an update, then you can also provide information for
the “What’s new in this Version” section.
4. Submission
Preparation
Preparation
The submission process has become much easier since
the release of Xcode 4. You can now validate and submit an application using
Xcode, for example. First, however, you need to create your application in
iTunes Connect.
the release of Xcode 4. You can now validate and submit an application using
Xcode, for example. First, however, you need to create your application in
iTunes Connect.
Visit iTunes Connect, sign in with your iOS developer account, and
click “Manage Your Apps“ on
the right. Click the “Add New App“
in the top left, select “iOS App”,
and fill out the form.
click “Manage Your Apps“ on
the right. Click the “Add New App“
in the top left, select “iOS App”,
and fill out the form.
Step 1: Basic Information
The App Name, which needs to be unique,
is the name of your application as it will appear in the App Store. This can be
different than the name that is displayed below your application icon on the
home screen, but it is recommended to choose the same name. The SKU
Number is a unique string that identifies your application. I usually
use the application’s bundle identifier. The last piece of information is the Bundle
ID of your application. This means selecting the (wildcard or
explicit) App ID that you created earlier from the drop down menu.
is the name of your application as it will appear in the App Store. This can be
different than the name that is displayed below your application icon on the
home screen, but it is recommended to choose the same name. The SKU
Number is a unique string that identifies your application. I usually
use the application’s bundle identifier. The last piece of information is the Bundle
ID of your application. This means selecting the (wildcard or
explicit) App ID that you created earlier from the drop down menu.
Step 2: Price and Availability
In the next step, you specify your application’s
price and availability. Apple works with price tiers so that you don’t have to
specify a price for each country that Apple operates in. You can also specify
in which stores your application should – or shouldn’t – be available. The
information that you enter in this step can be modified once your application
is live in the App Store. In other words, you can change the price and availability
of an application without having to submit an update.
price and availability. Apple works with price tiers so that you don’t have to
specify a price for each country that Apple operates in. You can also specify
in which stores your application should – or shouldn’t – be available. The
information that you enter in this step can be modified once your application
is live in the App Store. In other words, you can change the price and availability
of an application without having to submit an update.
Step 3: Metadata
We’ve already covered the application’s metadata.
The only aspect that I haven’t talked about yet is your application’s rating.
Based on your application’s content and functionality, it is given a rating.
This rating is not only useful for telling users about your application’s
content and features, the rating is also used by the operating system for the
parental controls features.
The only aspect that I haven’t talked about yet is your application’s rating.
Based on your application’s content and functionality, it is given a rating.
This rating is not only useful for telling users about your application’s
content and features, the rating is also used by the operating system for the
parental controls features.
It is strongly recommended that you don’t try to
outsmart the rating system. Apple is well aware of this and will reject your
application if it doesn’t agree with the rating that you have set.
outsmart the rating system. Apple is well aware of this and will reject your
application if it doesn’t agree with the rating that you have set.
Step 4: Ready to Upload Binary
Once your application’s metadata is submitted, you
will be presented with a summary of your application. Under Versions,
you should see the version that you submitted a moment ago. Click the View
Details button and click the Ready to Upload Binary button
in the top right. You are then asked one or more questions regarding your application
and, if all went well, you should see a message telling you that you are now
ready to upload your application binary. The status of your application has
changed to Waiting for Upload.
will be presented with a summary of your application. Under Versions,
you should see the version that you submitted a moment ago. Click the View
Details button and click the Ready to Upload Binary button
in the top right. You are then asked one or more questions regarding your application
and, if all went well, you should see a message telling you that you are now
ready to upload your application binary. The status of your application has
changed to Waiting for Upload.
5. Uploading
Binary
Binary
To submit your application, you need to create
an archive of your application. You can only create an archive
by building your application on a physical device. If you select
the iOS Simulator in the active scheme, you will notice that the Archive option
in Xcode’s Product menu is grayed out. Connect an iOS device
to your Mac, select it in the active scheme, and select Archive from
Xcode’s Product menu.
an archive of your application. You can only create an archive
by building your application on a physical device. If you select
the iOS Simulator in the active scheme, you will notice that the Archive option
in Xcode’s Product menu is grayed out. Connect an iOS device
to your Mac, select it in the active scheme, and select Archive from
Xcode’s Product menu.
If all went well, you should now have an archive
and Xcode’s Organizer should automatically open and show you the archive you
just created. Select the archive from the list and click the Distribute… button
on the right. From the options you are presented with, select Submit to
the iOS App Store. After entering your iOS developer account credentials
and selecting the Application and Code Signing Identity,
the application binary is uploaded to Apple’s servers. During this process,
your application is also validated. If an error occurs during the validation,
the submission process will fail. The validation process is very useful as it
will tell you if there is something wrong with your application binary that
would otherwise result in a rejection by the App Store review team.
and Xcode’s Organizer should automatically open and show you the archive you
just created. Select the archive from the list and click the Distribute… button
on the right. From the options you are presented with, select Submit to
the iOS App Store. After entering your iOS developer account credentials
and selecting the Application and Code Signing Identity,
the application binary is uploaded to Apple’s servers. During this process,
your application is also validated. If an error occurs during the validation,
the submission process will fail. The validation process is very useful as it
will tell you if there is something wrong with your application binary that
would otherwise result in a rejection by the App Store review team.
6. Waiting
If the submission process went without problems,
your application’s status will change to Waiting for Review. It takes
several days for Apple to review your application and the time it takes, tends
to fluctuate over time.
your application’s status will change to Waiting for Review. It takes
several days for Apple to review your application and the time it takes, tends
to fluctuate over time.
Conclusion
The submission process is quite lengthy for a new
application, but submitting an update to the App Store is much less cumbersome.
Keep in mind that the submission process is much more involving if your
application is localized in various languages as your application’s metadata
needs to be localized as well. However, localizing your application is well
worth the effort as it often results in higher sales and positive customer
feedback.
application, but submitting an update to the App Store is much less cumbersome.
Keep in mind that the submission process is much more involving if your
application is localized in various languages as your application’s metadata
needs to be localized as well. However, localizing your application is well
worth the effort as it often results in higher sales and positive customer
feedback.
Post a Comment