Android 14 changes for developers and what they mean for your apps
Android 14 (API level 34), released in October 2023, introduced a set of changes that affect how apps run, request permissions, and work in the background. Many of these changes only apply once your app targets API 34, which Google Play has required for new apps and updates since August 31, 2024. Play’s target level has since moved higher, so these Android 14 rules are now the baseline for every app on the store. Here are the changes that matter most.
What new APIs and features did Android 14 add?
- Credential Manager and passkeys: A single API for passwords, passkeys, and federated sign-in, making passwordless login easier to build.
- Partial photo and video access: Users can grant access to only selected photos and videos through the new READ_MEDIA_VISUAL_USER_SELECTED permission.
- Ultra HDR images: Support for 10-bit HDR photos stored in a backward-compatible JPEG format.
- Screenshot detection: A privacy-friendly API that tells your app when a user takes a screenshot of it.
- Regional preferences and grammatical inflection: APIs that let apps respect user choices for units, first day of the week, and gendered language in translations.
- Non-linear font scaling: Text can scale up to 200%, with large text growing less than small text, so apps should use sp units and test large font sizes.
- Predictive back: In-app predictive back animations became available to developers.
- User-initiated data transfer jobs: A JobScheduler job type for large uploads and downloads the user starts.
Which behavior changes affect existing apps?
- Foreground service types are required: Apps targeting API 34 must declare a type, such as dataSync, location, or mediaPlayback, for each foreground service and hold the matching permission.
- Exact alarms denied by default: SCHEDULE_EXACT_ALARM is no longer pre-granted to most newly installed apps targeting API 34. Use inexact alarms or WorkManager when possible.
- Safer implicit intents: Implicit intents are only delivered to exported components, and mutable PendingIntents must not use implicit intents.
- Runtime-registered broadcast receivers: Apps must specify RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED when registering receivers at runtime.
- Safer dynamic code loading: Dynamically loaded code files must be marked read-only.
- Background activity launches: Apps need extra opt-ins before a PendingIntent can start activities from the background.
- Minimum installable target SDK: Android 14 blocks installing apps that target API levels below 23.
- Cached app broadcasts: Context-registered broadcasts can be queued while an app is cached, so they may arrive later.
How did background work change?
Android 14 continued pushing apps toward WorkManager and JobScheduler. Long-running work must use the right foreground service type or a user-initiated data transfer job, and the system is quicker to limit work from cached apps. If your app depends on periodic syncing, use WorkManager with constraints and handle delays without losing data.
How should developers test for Android 14 compatibility?
- Use a current Android Studio release and install the API 34 SDK and emulator images.
- Set targetSdk to 34 or higher and fix compiler and lint warnings about foreground service types, receivers, and intents.
- Test permission flows, especially partial photo access and exact alarms.
- Use the compatibility framework toggles in Developer options to enable Android 14 behavior changes one at a time.
- Test large font sizes up to 200% and check layouts.
- Update libraries to versions that support API 34.
Conclusion
Android 14’s biggest developer changes were required foreground service types, stricter rules for intents, receivers, and exact alarms, partial media access, and new APIs such as Credential Manager. Because Google Play now requires targets above API 34, every app on the store has to follow these rules, so they are worth knowing even if you are working on the latest Android version.
Frequently Asked Questions
Do I have to target Android 14?
Google Play required API 34 for new apps and updates from August 31, 2024, and the requirement has since moved to newer API levels. To publish updates, your app must target at least the level Play currently requires.
Will Android 14 break my app if I don’t update it?
Many changes only apply when you target API 34, so older apps usually keep running. But some changes affect all apps, such as the block on installing apps that target API levels below 23, so test on Android 14 and newer devices.