iOS app development

From build to the App Store

1. 01

   Developer account

   Apple Developer Program membership in your organisation's name.

   Output: Distribution access

2. 02

   TestFlight

   Internal testers, then external testers once the build is approved for testing.

   Output: Beta feedback

3. 03

   Submission

   Build, listing, privacy details and review notes.

   Output: In review

4. 04

   App Review

   Apple reviews the app against its guidelines.

   Output: Approved or changes requested

5. 05

   Release

   Released manually, automatically or gradually.

   Output: Live on the App Store

Guidelines that often shape an app

Digital purchases and physical goods

Apple's guideline 3.1.1 says that unlocking features or functionality within an app, such as subscriptions, premium content or a full version unlock, must use in-app purchase rather than your own payment mechanisms. That affects how membership and content apps are designed and priced, so check Apple's current terms for in-app purchase. Physical goods and services used outside the app are the opposite case: guideline 3.1.3(e) says they must be paid for by methods other than in-app purchase, such as Apple Pay or card entry. Check the current guidelines for your exact model before designing the purchase flow.

Getting this wrong is a common cause of rejection, so decide early.

Using TestFlight well

Designing for iPhone and iPad

• Platform conventions

  Navigation and controls that feel natural to iPhone users.

• iPad layouts

  Decide whether to support iPad and design for its space.

• Accessibility

  Dynamic text sizes and VoiceOver support.

• Permissions

  Clear explanations when asking for camera, location or notifications.

Accounts and internal apps

Apps distributed on the App Store need an Apple Developer Program membership, which Apple lists at $99 a year. Organisations distributing proprietary apps only to their own employees can consider Apple's Enterprise Program, listed at $299 a year; check Apple's eligibility requirements carefully, and discuss other private distribution options with whoever manages your devices. Whatever the route, the membership should be held by your organisation.

Phased releases on iOS

App Store Connect offers a phased release for automatic updates. Apple's documentation describes it rolling out over seven days, starting with a small percentage of users with automatic updates and rising to everyone, with the option to pause for up to 30 days in total. Anyone can still download the update manually, so it limits rather than prevents exposure. Combined with crash reporting, a phased release gives time to spot problems before most users are affected.

Use it for significant updates in particular.

Planning for review in launch dates

Because every submission is reviewed, launch dates should allow time for review and for a possible resubmission if Apple asks for changes. Submitting a well-tested build with clear review notes and a working test account reduces delays. For time-sensitive launches, such as a campaign or an event, submit well ahead and hold the release until the planned date.

Testing on Apple devices

Test on a few iPhone sizes, including an older model your users still carry, and on iPad if you support it. Check behaviour on the newest iOS version as soon as Apple releases it, because changes can affect permissions, notifications and layouts.