iOS 27 and the Android 16 Deadline: How to Test Your App This Fall

If you ship a mobile app, the last three weeks changed what you need to test. Google Play's new target API requirement took effect on August 31, and Apple opened App Store submissions for iOS 27 on September 9 ahead of the public release it set for Monday, September 14. Both changes alter how apps behave on real phones, and neither one waits for your next planned release.

The short answer

Retest your app on the new operating systems now, not when you next ship a feature. On Android, moving to API level 36 changes how your app handles screen edges, the back gesture and large screens. On iOS, customers start updating within days, and Apple has already said that from April 2027 every upload must be built with the iOS 27 SDK. Build a short test pass around those changes and run it before your next update goes out.

What changed in the last month

Google also lets developers request an extension to November 1, 2026. An extension buys time to update. It is not a test plan, and the behavior changes below still arrive the day you raise your target.

The Android 16 changes that break apps

Google's own documentation lists the changes that apply once an app targets API level 36. Three of them catch the most apps.

Edge to edge is no longer optional. Apps targeting Android 15 could opt out of drawing behind the status and navigation bars. For apps targeting Android 16 and running on Android 16, that opt out is disabled. Test every screen for buttons, headers and text fields hidden under the system bars or the keyboard.

Predictive back is on by default. For apps targeting Android 16 on Android 16 devices, the system back animations are enabled and the old back button callback is no longer called. If your app intercepts back to confirm leaving a form, close a sheet or save a draft, that code may silently stop running. Test the back gesture on every screen where it should do something other than leave.

Large screens ignore your orientation lock. On displays at least 600dp wide, such as tablets, foldables and desktop windows, Android 16 ignores orientation, resizability and aspect ratio limits for apps that target it. An app designed only for portrait will fill the whole window and rotate. Google warns about stretched layouts, off screen elements and lost state when the screen rotates. There is a temporary opt out, but Google states it will not apply once an app targets API level 37.

What iOS 27 means for testing

Apple's September 9 developer announcement and its event the same day point to four practical items.

1. No iPhones were dropped. iOS 27 supports every device that runs iOS 26, which reaches back to the iPhone 11 series and the second generation iPhone SE. Your oldest supported phone is now running the newest system, and that pairing is where performance and layout problems tend to show up.
2. New hardware joins the matrix. Apple announced new models alongside the release, including the iPhone 18 Pro, iPhone 18 Pro Max and iPhone Duo. Check screen size and layout on whichever new model your customers are most likely to buy, through the simulator if you do not have the device yet.
3. App Store Connect asks new questions. Apple added age rating questions, and apps with social media features need to indicate them. A wrong answer is a release blocker, so treat the store listing as part of the test pass.
4. The SDK deadline is set. From April 2027, iOS and iPadOS uploads must be built with the iOS 27 SDK or later. A rebuild with the new SDK can change behavior even when your code does not change, so plan that rebuild and its full test pass well before spring.

On the Mac side, Apple said macOS 27 runs only on Apple silicon. If you ship a Mac app, you can stop testing Intel builds for macOS 27, but do not drop them from older macOS versions without checking who still uses them.

A short test pass for this release season

Run this on your current production build before your next update, so you know which problems are new.

1. Install the new systems on real devices. Put iOS 27 on one older and one current iPhone, and Android 16 or later on one phone and one tablet or foldable.
2. Walk your revenue flows first. Sign up, sign in, purchase or booking, and account settings. These are where a broken button costs real revenue.
3. Check edges and the keyboard. On every screen with a form, open the keyboard and confirm the submit button and error messages are visible.
4. Test the back gesture on Android. On each screen with unsaved input or an open sheet, swipe back and confirm the app does what you intended.
5. Rotate and resize on a large screen. Rotate mid form, split the screen, and confirm nothing stretches off screen and nothing typed is lost.
6. Use the largest text size and dark mode. OS updates often shift fonts and colors. Long labels should wrap, not cut off.
7. Interrupt the app. Take a call, background the app, lose signal and return. Confirm the work is still there.
8. Check notifications and permissions. New systems sometimes reset or reword permission prompts. Confirm the first run experience still makes sense.
9. Watch crash reports for two weeks. Customer adoption of a new OS ramps over days. Review crash and error reports daily until the curve settles.

How to schedule it

Treat the fall operating system releases as a standing event on your calendar, the same way a retailer plans for the holidays. Apple and Google publish betas months ahead, and the deadlines are announced in writing. Add a release season test pass every August and September, keep a written list of the behavior changes you checked, and require it before any update ships. The teams that get caught are rarely surprised by the change itself. They are surprised that nobody owned testing it.

Getting help with release season testing

HQ Labz helps businesses test their mobile and web apps against new operating system releases and store requirements before customers find the problems. It starts with a free discovery call and a written quote stating hours, price and timeline before any work begins.

Talk to us about testing your app

Questions people ask

What is the Google Play target API level requirement for 2026?

From August 31, 2026, new apps and app updates on Google Play must target Android 16, API level 36, or higher. Existing apps must target Android 15, API level 35, to stay available to new users. Developers can request an extension to November 1, 2026.

Do I need to update my app for iOS 27?

You do not have to rebuild immediately, but you should test your current version on iOS 27 now because customers update within days. From April 2027, Apple requires iOS and iPadOS uploads to be built with the iOS 27 SDK or later.

What breaks when an Android app targets API level 36?

The most common problems are content hidden behind system bars because edge to edge can no longer be turned off, back gesture handling that stops running because predictive back is on by default, and layouts that stretch or lose state on tablets and foldables.

Which devices should I test on after a new OS release?

At minimum, test the oldest phone you support and a current model on the new system, plus one Android tablet or foldable. Then check the devices your own analytics show your customers use most.

Sources

1. Google Play Console Help. Target API level requirements for Google Play apps.
2. Android Developers. Behavior changes: apps targeting Android 16 or higher.
3. Apple Developer News. App Store submissions now open for the latest OS releases. September 9, 2026.
4. 9to5Mac. Apple confirms iOS 27 release date: September 14. September 9, 2026.
5. MacTech. App Store submissions now open for the latest OS releases. September 10, 2026.