Both major mobile platforms have moved this autumn, and each has deadlines attached. Apple's iOS 27 SDK is open for App Store submissions, Google Play's new target API rule took effect on 31 August, and Android 17 brings behaviour changes that will catch apps that were never tested on large screens. If you ship an app, here is what needs doing, in what order, and what can wait.
Apple: build with the iOS 27 SDK by April 2027
Apple's developer news says App Store submissions are open for the latest OS releases: iOS 27, iPadOS 27, macOS 27, tvOS 27, visionOS 27 and watchOS 27. It also sets the enforcement date. From April 2027, iOS and iPadOS apps must be built with the iOS 27 and iPadOS 27 SDK or later, with matching minimums for tvOS, visionOS and watchOS.
According to 9to5Mac's report, Apple also reminded developers to:
answer new age rating questions, including for features like Time Allowances
update App Store listings with new product page headers and search result assets that follow its updated design guidance
Note that April 2027 is not an emergency, and it is also not far off. Apple applied the same kind of rule this year: as Appbot's summary notes, all submissions had to use the iOS 26 SDK from 28 April 2026. Existing apps can stay in the store without updates, but any update you submit must meet the rule.
Google Play: target API 36 is already required
Per the Google Play target API requirements, starting 31 August 2026:
New apps and updates must target Android 16 (API level 36) or higher. Wear OS and Android Automotive OS apps need API 35 or higher, and Android TV and XR apps need API 34 or higher.
Existing apps must target Android 15 (API level 35) or higher to remain available to new users on devices running newer Android versions.
Developers who need more time can request an extension until 1 November 2026.
If you have not updated yet, that extension date is a month away. Check the Play Console for any warnings on your apps this week.
android {
defaultConfig {
targetSdk = 36
}
}Raising the target level is the easy line; the hard part is testing what changes at that level.
Android 17: changes to test now
Android 17 is API level 37. You are not required to target it yet, but the platform's behaviour changes for apps that do are a good preview of your next migration, and some changes apply to every app running on Android 17 devices. The ones most likely to affect real apps:
Large screens. Apps targeting Android 17 can no longer opt out of the platform ignoring orientation, aspect ratio and resizability restrictions on large screens (smallest width of 600dp or more). If your app locks to portrait, expect it to be resized on tablets and foldables.
Local network permission. A new runtime permission,
ACCESS_LOCAL_NETWORK, becomes mandatory for apps targeting Android 17. Apps that talk to smart-home devices, printers or casting targets will need to request it or use system device pickers.SMS OTP protection. Certain one-time-password messages are delayed by three hours for apps that are not the intended recipient. Google recommends moving to the SMS Retriever or SMS User Consent APIs.
Background audio. Audio playback, focus and volume calls from invalid lifecycle states now fail, so media and alarm apps should be tested.
Memory limits. Android 17 enforces device-specific app memory limits, and apps that exceed them may be terminated.
<uses-permission android:name="android.permission.ACCESS_LOCAL_NETWORK" />Because the SMS OTP and memory changes affect all apps, they can hit you even if you have not raised your target level.
A sensible order of work
This week: confirm your Android apps target API 36. If not, raise it now or request the extension.
October: run your app on an Android 17 emulator, including a tablet or foldable profile. Look for layouts that break when rotated or resized.
October: if you rely on SMS OTP auto-fill, move to the recommended APIs before your users notice delayed codes.
Before 1 November: finish anything you asked the extension for.
Winter: build with Xcode 27, refresh your App Store product page assets and answer the new age-rating questions.
Before April 2027: make sure your release pipeline produces iOS 27 SDK builds by default.
The takeaway
Platform changes become support tickets long before they become roadmap items. Spend a couple of hours this week on the ones with dates attached, then schedule the Android 17 testing while the fixes are still cheap.