How to release an iPhone app: a 30-day plan (2026)

By Sigsten Gustavii· 16 September 2026· Updated 27 October 2026· 9 min read

An app that appears on the App Store with no warning is usually met with silence. A month of preparation changes that: testers catch the worst bugs, the product page is ready to convert, Apple's editors have heard about the app, and the people you told are waiting for it.

This plan splits the month into four weeks plus release day and the two weeks after. It assumes the app works and you are a member of Apple's Developer Program. Every Apple detail comes from Apple's own pages, read in October 2026.

Week 1 (days 30 to 23): test with real people

Before anyone can review, buy or praise the app, it has to work for people who are not you. Apple's TestFlight is the tool for this. You can invite up to 100 people from your App Store Connect team as internal testers and up to 10,000 external testers, by email or with a public link. The opening build for external testers goes through Apple's Beta App Review, and each build can be tested for 90 days.

1. Upload a build to App Store Connect and wait for it to finish processing.
2. Invite ten to twenty people who match your audience, not only friends.
3. Give them one task, such as "plan next week's meals", and ask where they got stuck.
4. Fix crashes and confusion, upload again, and repeat once.

Our post on TestFlight explains internal and external testing in detail.

Week 2 (days 22 to 16): the product page and Apple's editors

The product page is where every link you share lands, so build it while testers are busy. Write a name and subtitle of up to 30 characters each, choose keywords that match real searches, and make screenshots that each show one benefit. Add the privacy policy and support URL Apple asks for. Our App Store optimization guide walks through each field.

This is also the week to tell Apple. With Featuring Nominations in App Store Connect you can share a new app with Apple's editorial team. Apple asks for at least two weeks' notice and suggests up to three months for wider consideration, so a nomination sent now, sixteen days or more before release, still counts. Say what the app does, who it is for, and what is new about it.

Week 3 (days 15 to 8): App Review and your release option

Submit the finished version for review with time to spare. Apple says it reviews about 50% of submissions in under 24 hours and 90% in under 48, but a rejection and a resubmission can take several more days, so a week of buffer is wise. Fill in App Review Information completely, with a demo account if the app has sign-in. Our App Store submission checklist lists what reviewers look for.

When you submit, choose how the version goes live: automatically when approved, on a date you set, or manually. Pick manual. It lets you choose the hour, and Apple notes that a manual release may take up to 24 hours to appear everywhere, so release a day before you announce.

Optional: open pre-orders

If you want people to commit before release day, Apple lets a brand-new app take pre-orders. Your app's product page goes live with an order button, and on release day the app downloads by itself on the devices of everyone who pre-ordered, with a notification.

You set it up in App Store Connect under Pricing and Availability, by choosing Publish as Pre-Order. Apple's tips: put a clear "Pre-order on the App Store" link everywhere you post, use the pre-order badge in your marketing, and avoid announcing a date you might have to move. App Analytics then shows pre-orders by date, region and source, so you can see which posts worked.

A pre-order is optional. For a small free app, a short countdown with a release-day post often does as well. For a paid app or one with a community already waiting, it turns interest into installs that land on day one by themselves.

Week 4 (days 7 to 1): tell people

• A press kit: one page with what the app does, why you made it, screenshots, the icon and an email address.
• Personal emails to writers and creators who cover your kind of app. For a paid app, include a promo code: Apple allows up to 100 per version of each platform, each valid for four weeks.
• Short videos of the app solving a real problem, posted in the days before release.
• Communities where your audience already talks, with a note that you made something for them and when it arrives.
• A list of people to tell on the day: testers, friends, anyone who asked to know.

Our guide to promoting an app with no budget covers each of these in more depth.

Release day

1. Release the version by hand in App Store Connect the evening before you announce, so it has time to appear in every region.
2. Check the live product page on a real iPhone: search for the app's name, open it, install it.
3. Post everywhere at once: your list, your communities, your videos, with the App Store link.
4. If you used Product Hunt, post there and stay to answer every comment.
5. Answer everything for the whole day: comments, emails, replies. Early questions are your next update.

The two weeks after: reviews, ratings and a fix

The days after release decide whether the app keeps growing. People who installed on day one will find bugs, ask for features and leave the earliest reviews. Use that attention.

• Reply to reviews in App Store Connect. The reviewer is notified and can update their review, and a polite fix-and-reply often turns a one-star review around.
• Ask for ratings at the right moment, with Apple's own prompt, after someone completes something. The system shows it at most three times in 365 days. Our guide to getting more App Store ratings explains the rules.
• Ship a fix release within two weeks with the top complaints solved. Use phased release so it reaches people with automatic updates over seven days, 1% on day one up to 100% on day seven, and pause it if anything goes wrong.
• Plan an in-app event for week three or four: it can be promoted up to 14 days ahead and appears on your product page and in search.
• Read App Analytics to see where installs came from, and do more of what worked.

Releasing an app built with Borel

With Borel you describe an iPhone app in plain words, Borel writes it in Swift, and you try it on a live iPhone in your browser, free. When it is ready, the whole release runs from one window:

1. Run review: a check of the build for App Review risks before anything goes to Apple.
2. Your app: the name, icon, category, screenshots, description and a phone number for Apple's reviewer, one question per screen.
3. Ready to send: a list of everything Apple needs, each ticked or crossed with a reason, and a Fix button for each cross.
4. Sign in to Apple with your App Store Connect account; Borel sets the app up there for you.
5. Send to Apple: Xcode builds, signs and uploads the app on Borel's Mac, so you need no Mac of your own. The build appears in TestFlight once Apple has processed it.
6. Submit for review from the same window, with the reviewer's phone number filled in. If the app has accounts in Borel's cloud, Borel checks the reviewer's demo account before each submission and recreates it if needed.

Borel then shows the app's live review status read from Apple. Pre-orders, the featuring nomination and the release button are in App Store Connect, under your own account. Fixes after release are a message away: describe the problem, check it on the live iPhone, and publish the update.

Publishing takes Borel Pro, from $20 a month, and Apple's Developer Program, $99 a year. The publishing guide in Learn shows each screen, and publishing without a Mac explains the route from a Windows PC.

Three people said they couldn't find how to delete an entry. Add a swipe-to-delete on each row, with an Undo banner for five seconds, and a Delete button on the detail screen.

The bottom line

A good release is mostly preparation: a week of testing, a week on the product page and a featuring nomination, a week for App Review with a manual release, and a week of telling people. A pre-order is a strong option for a new app with an audience already waiting. After release day, reply to every review, ask for ratings at the right moment, and ship a fix within two weeks. If the app is not built yet, start with Borel and give it the month it deserves.

I think the weeks after release matter more than the day itself, because that is when you learn what people actually want. Start the plan, and tell me where it took you.

– Sigsten

Make your iPhone app in Borel

Describe the app you want and see its first screens before you pay anything.