Chapters

Hide chapters

Catalyst by Tutorials

First Edition · iOS 13 · Swift 5.1 · Xcode 11

Before You Begin

Section 0: 3 chapters
Show chapters Hide chapters

13. Releasing on the App Store
Written by Marin Bencevic

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now

If you’re reading this book in order, by now you have a pretty good grasp of how to bring an iPhone or an iPad app to macOS. Now it’s time for the next step: Getting the app in the hands of users.

The good thing about Catalyst is that once you have a Mac app, it’s your choice what to do with it. There are three ways you can distribute your app to your users:

  • The App Store: The Mac App Store works almost the same way as the one on iOS. All existing iOS apps already follow Apple’s app review guidelines, so you should have no issues going through app review.
  • Third Party Distribution: As long as you sign the app and get it notarized by Apple, anyone can simply download and launch the app. The distribution, in this case, is up to you.
  • Developer Signing: Similar to third party distribution, this option requires that you sign your app with a development certificate. The certificate includes a whitelist of specific devices that can install the app, so you can’t use this for distributing to the general public. Since macOS doesn’t have TestFlight support, this is your best bet for testing the app while it’s in development.

The App Store vs. third party distribution

Since developer signing is only for testing, you’re probably trying to decide whether to use the App Store or distribute the app on your own. There are pros and cons to each approach. The App Store has several benefits including:

  • Apple manages the storage and distribution of the app.
  • Apple handles payments, including the initial purchase of the app, in-app purchases and subscriptions. They also manage complaints and refunds.
  • There’s a chance that Apple might feature your app, giving you access to a lot of users that otherwise might not have heard of the app.
  • You get access to App Store’s analytics and crash reporting with no additional effort.

That said, distributing on the App Store does come with downsides:

  • Most notably, Apple takes a cut from all App Store sales (30%), subscriptions (30% then 15% after a year) and in-app purchases of digital goods (30%).
  • You’re tying the app’s destiny to Apple’s. If they decide to move the App Store in a different direction, you get no say. Apple could potentially hurt your sales or make your app unavailable.
  • It limits your business model options. Offering dynamic or tiered pricing, enterprise deals or other more creative business models can be difficult or impossible.

While Apple takes a sizable cut of your income, it also gives you the most convenient way to sell your app. It’s your choice whether to invest significant effort and be the master of your destiny or save time by letting Apple take care of distribution for you.

If you really can’t decide, Apple lets you sell your app on your own and on the App Store at the same time.

The chapter you’re reading right now will teach you how to distribute your app on the App Store. The next chapter deals with distributing your app on your own. If you need help deciding, read both chapters and see how you feel after you know what goes into both approaches.

In other words, now that you’ve got your app — it’s time to make it rain!

Distributing on the App Store

The process of distributing your app via the App Store is tedious but simple. All you have to do is click a bunch of things! Before you get started, take note of some basic terminology you’ll need when going through this process.

Code signing

Xcode does a good job of automatically code signing your app. As the name suggests, code signing is a way of verifying that you’ve written the code inside the app and it hasn’t changed since you wrote it. Code signing is required before a user can install an app on a device. Your signature is a distribution certificate which you get from Apple and is unique to your developer account.

Setting up an app ID

The first thing you need to do is create an app ID for your app. You can do that in Apple’s developer portal. Head over to developer.apple.com, and click on Account in the top-right corner. Log in with your Apple Developer ID.

Adding an app entry

App Store Connect is where your app’s binary meets the App Store. This is where you create new App Store apps, add data like the app title, description and screenshots and — most importantly — upload and release the app.

Uploading a build

Now that you have an app entry, it’s time to go back to Xcode to upload a new build of your app to App Store Connect.

Pricing your app

While you’re in the App Store tab, head over to Pricing and Availability in the sidebar. You can set up the price of your app under Price Schedule. You can choose from almost 100 different pricing tiers for your app. Each of the tiers has a roughly similar price in all currencies. Once you select a price you can click on Other Currencies to see the exact values in each territory.

Submitting for review

Once you’ve filled everything out, click Save in the top-right corner and then click Submit for Review. A reviewer from Apple will take a look at your app to make sure you’re following the guidelines. This can take up to a few days. I know, there’s something very frustrating about having a completed app that’s just sitting there waiting to be reviewed. Hang in there!

Key points

  • You must sign each app with a provisioning profile, which combines a certificate with an app ID.
  • You create app IDs in Apple’s Developer Portal.
  • Manage the app on the App Store by going to App Store Connect.
  • Upload new builds from Xcode.

Where to go from here?

To make sure you’re not violating any of Apple’s guidelines, make sure to carefully read through Apple’s App Store Review Guidelines: apple.co/1lz8Lit. Apple also provides a helpful list of common app rejection reasons, which you can use as a checklist before submitting: apple.co/2ltWgeB.

Have a technical question? Want to report a bug? You can ask questions and report bugs to the book authors in our official book forum here.
© 2024 Kodeco Inc.

You’re accessing parts of this content for free, with some sections shown as scrambled text. Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now