iOS 27 Is Out: What App Owners Need to Do Before April 2027
Apple released iOS 27 on September 14, 2026, per Apple's newsroom announcement. If you own an iPhone app, nothing happened to it today. It is still on the App Store, and the version your customers installed still runs. What changed is the paperwork around your next update, plus one hard deadline that is now on the calendar.
Here is the short version. From this month, every app update you submit must answer a new question about social media features. From April 2027, every upload must be built with the iOS 27 SDK. And if your app uses Sign in with Apple, someone should check one line of email validation before the end of the year. Everything else can wait for a normal release.
What did not change today
It is worth being precise, because the launch coverage makes it sound more urgent than it is for most business apps.
Apple does not pull apps from the store because a new iOS version shipped. Your existing build keeps working unless it hits a bug on the new system, and that is something you find out by testing, not something Apple enforces. You are also not required to rebuild with Xcode 27 today. Since April 28, 2026, the minimum for uploads has been the iOS 26 SDK, and that remains the rule until next spring.
So the right reaction is a checklist, not a rush job.
The new requirement already in force: the social media question
This is the one that catches people, because it blocks a submission rather than breaking the app.
In June, Apple announced Time Allowances, which let parents set daily time limits across Entertainment, Games and Social Media apps. To sort apps into those buckets, Apple added questions to the age rating questionnaire in App Store Connect. Per Apple's July 2026 developer notice, "beginning in September 2026, responses will be required when submitting new apps or updates to the App Store." In practice, the next time anyone on your side tries to ship even a one-line bug fix, App Store Connect will want this answered first.
The question hinges on Apple's definition. A social media capability is "the ability to redistribute, amplify, or interact with user-generated content through a social feed or similar discovery method." Apple's Time Allowances announcement adds that this means a feed or discovery method "that visibly spreads content to many users." It applies regardless of which App Store category you picked.
What your answer does, per that same page:
- If you answer yes, your app goes into the Social Media Time Allowance category, gets a minimum age rating of 13+, and shows a new Social Media content descriptor on its product page.
- If you answer yes but disable those features for anyone under 13, your app stays out of the Social Media category for younger users. You must then use Apple's Declared Age Range API to check users' age ranges, and your other questionnaire answers decide your final rating.
- If you answer no, your rating comes from the rest of the questionnaire as before.
Which way most business apps should answer
As an illustrative scenario, take a booking app where customers schedule appointments and message the business. Nothing a customer writes is spread to other customers, so it does not fit the definition. Now add a public community wall where members post photos that other members like and comment on. That is user-generated content spread to many users through a feed, and the honest answer becomes yes.
The in-between cases are the ones to think about carefully: public reviews, a leaderboard with user profiles, a comments section under content. Read the definition against what your app actually does, not what its category says. If you still cannot tell, contact Apple through the Contact Us page in App Store Connect rather than guessing. A 13+ rating changes who can find your app, so it should be a decision you make on purpose, not something you discover on your product page.
The deadline on the calendar: April 2027
Apple's announcement opening iOS 27 submissions sets the next floor. Starting April 2027, iOS and iPadOS apps uploaded to App Store Connect must be built with the iOS 27 and iPadOS 27 SDK or later. Apple has not published an exact day yet, so plan for the start of the month.
Like the Android rule we covered in the Google Play target API post, missing it does not remove your app. It freezes it. You can no longer upload any update, including an urgent fix, until the app has been moved to the new toolchain.
The reason not to leave this until March is that an SDK upgrade is rarely one step. A new Xcode often means updating the libraries your app depends on, and one outdated library can force several more. That is routine work in October. In the week a payment integration breaks, it becomes an emergency. We walk through that failure pattern in what happens if you never update your app.
Sign in with Apple is getting a new email domain
If your app offers Sign in with Apple and a user chooses to hide their email, Apple gives your app a private relay address. Per Apple's August 24, 2026 update, starting later this year new addresses will be issued on private.icloud.com instead of privaterelay.appleid.com. Existing addresses keep working.
Most apps will not notice. The ones that will are apps whose backend checks the email domain, keeps an allowlist, or treats relay addresses specially for things like receipts and notifications. For those, a new user signing in after the switch may be rejected or mishandled with no error on the user's screen. Apple has not given a date, so ask your developer to check that code now. It is usually a small change.
New product page assets are coming, not required
The same Apple notice mentions new product page headers and search result assets, plus a preview tool in App Store Connect marked "coming soon." Nothing here is mandatory. If your listing already converts, leave it until the tools actually arrive. When you do revisit it, the rules for the assets that do get enforced are in our guide to App Store screenshot requirements.
What to do this week
- Answer the social media question in App Store Connect now, before you need to ship something. It takes minutes when nothing is on fire.
- Install your current App Store build on a device running iOS 27 and walk through sign-up, login, payment and your main screens. You are looking for anything that looks or behaves differently.
- Ask whoever maintains the app for an SDK upgrade date that lands well before April 2027, in writing.
- If you use Sign in with Apple, ask whether anything checks the relay email domain.
- Confirm you can log into App Store Connect yourself. If only a former developer can, fix that first. We explain why in who owns your app.
When you do not need outside help
If you have a developer on staff, none of this is a project. It is two calendar entries and a ten-minute questionnaire, and paying an agency for it would be a waste. The same goes for apps with no Sign in with Apple and no user-generated content: answer no, test on iOS 27, and schedule the SDK upgrade into your next planned release.
Where it gets harder is an app that has not been touched in a year or more, or one whose original developer is gone. Then the SDK upgrade can uncover dependency work nobody budgeted for, and the ongoing cost picture in what it costs to run an app every month is worth reading before you commit.
If that describes your app, book a call and bring the date of your last App Store submission. That date tells us most of what we need to know about how much work April will be.
Your app. In the stores. Done for you. US APP Team designs, builds, and launches your iOS and Android app for a fixed price. Start your app brief or book a free intro call — both are free.
Want to poke around first? Every tool in our free tool library runs in your browser with no signup: an app cost calculator, an app name generator, and a privacy policy generator.
