Android 17 Is Out: New Features and What App Owners Must Update

Android 17 is no longer a beta. Google released it on 16 June 2026 on most supported Pixel devices, publishing the source code the same day, and said phones from other makers would follow in the coming months. The developer version number is API level 37. As of November 2026, point updates called 37.1 and 37.2 were still listed as beta tracks on Google's developer site.

This post separates what is new for users, what changes for every app, and what changes only when your developer raises the app's target to API 37. That last group is the one to plan around, and Google Play has not yet set a date for it.

New things users will notice

• App bubbles. Long-pressing an app icon can float that app as a small window above other apps, with a bubble bar on tablets and foldables.
• Continue On. A tablet taskbar suggests the app you last used on your phone and opens it where you left off.
• Contact picker. A built-in picker lets an app receive one chosen contact without being given your whole address book.
• Hearing aid routing. Users can send ringtones and alarms to a hearing aid or to the phone speaker.

For developers: memory limits and AppFunctions

Android 17 enforces app memory limits based on how much RAM the device has. An app that keeps too much in memory can now be ended by the system, and Google has a reporting label for it. Lighter, more frequent garbage collection and a rewritten message queue improve smoothness, though code that pokes at the queue's private parts can break.

The other headline is AppFunctions: a way for an app to expose actions, such as "create an invoice", that AI assistants like Gemini can call. Google's launch post describes the Jetpack library as alpha and the Gemini integration as a private preview. It is early; treat it as a direction, not a feature to promise customers.

Changes that apply once you target API 37

Google lists these as behaviour changes for apps that target Android 17 or higher:

• No opt-out on large screens. Orientation locks and fixed aspect ratios are ignored on screens of 600dp and wider, and the Android 16 escape hatch is gone. Games are exempt. Details are in our post on orientation changes on tablets and foldables.
• SMS one-time passwords are delayed. Standard SMS messages that contain an OTP are held back for about three hours from apps that are not the default messaging app. If your login reads OTPs from SMS, move to Google's SMS Retriever or SMS User Consent methods.
• Local network access needs a permission. Apps that reach printers, cameras or machines on the local Wi-Fi must ask for it, or use a system device picker that skips the prompt.
• Background audio is restricted. Playing sound, taking audio focus or changing volume in the background requires a running foreground service of the right kind.
• Certificate Transparency is on by default. Connections to servers with improperly logged certificates can fail.
• Native libraries loaded at runtime must be read-only. Otherwise the app throws an error.
• Home-screen widget images have a size budget. Oversized bitmaps now cause errors instead of warnings.

Activities also stop restarting on keyboard, touchscreen and similar configuration changes unless the app opts in. That is helpful, but state-handling code written around restarts deserves a look.

What is announced, and what is in force

The release is in force: Android 17 is on phones today. The target-based changes above are not in force for your app until you set the target to 37. Google Play's target API page, checked on 3 November 2026, lists Android 16 as the newest required level and shows no deadline for API 37. Do not trust anyone who quotes you one.

Play has announced related policy dates for apps that do target 37. By 27 January 2027, such apps must use the location button for one-time precise location unless they file a declaration. By 25 August 2027, using the local network permission requires a Play Console declaration. Our Play policy checklist covers the rest.

What to do now

1. Check whether your login reads OTP text messages, and plan a move to SMS Retriever if it does.
2. List any feature that talks to local devices, plays audio in the background, or draws home-screen widgets.
3. Test the current app on an Android 17 device or emulator before your next release.
4. Decide a quarter in which to raise the target to API 37, ideally combined with other planned work.

For most small businesses, the right move is to stay on Android 16 targeting until the next planned update, test on Android 17 now, and avoid emergency rework. VS Tech Builders handles this through the maintenance work described in our app maintenance guide; if you want a compatibility review, get in touch.

Sources

Checked on 3 November 2026. Technology changes quickly; always confirm details with the official source before you act on them.

• Android 17 is Here — Android Developers Blog
• Behavior changes: Apps targeting Android 17 or higher — Android Developers
• Android 17 overview — Android Developers
• Upcoming Android and Google Play deadlines — Android Developers

Frequently asked questions

When was Android 17 released?

Google released Android 17 (API level 37) on 16 June 2026 to most supported Pixel devices and published the source code the same day. Phones from other manufacturers receive it later, on each maker's schedule, so many of your customers will still be on Android 15 or 16 for some time.

Does Google Play require apps to target Android 17?

Not as of 3 November 2026. Google's target API page lists Android 16 (API 36) as the requirement for new apps and updates from 31 August 2026 and shows no deadline for API 37. When Google announces one, it will appear on that page and in Play Console notifications.

Will my app's OTP login stop working on Android 17?

Only if the app reads OTP text messages directly and targets API 37. Google delays standard SMS messages containing OTPs for about three hours for apps that are not the default messaging app. The fix is to use SMS Retriever or SMS User Consent. Apps still targeting an older version are not affected by this particular change.

What is AppFunctions and should I build for it now?

AppFunctions lets an app expose actions that AI assistants such as Gemini can call. Google describes the library as alpha and the Gemini integration as a private preview. For most businesses it is too early to build around. Watch it, and revisit once Google moves it to a stable release.