Way your app is built and the platform functionality it's using. Similarly, you should not need to use newĪPIs or change the app's compileSdkVersion, although this can depend on the Typically you can adjust your app and publish an update without needing toĬhange the app's targetSdkVersion.
Some platformĬhanges can affect the way your app behaves, so it's important to test earlyĪnd thoroughly, then make any needed adjustments to your app. Users updating to the latest version of Android. It's important to test the functionality of your existing app againstĪndroid 11 to ensure a great experience for Ready to get started, read Get Android 11. This page outlines the general steps for each of those phases.
Targeting the new platform features and APIs (as soon as possible after final release).Ensuring app compatibility (by Android 11 final release).Platform release timeline and ensures a great experience for your usersĪ typical migration has two phases, which can be concurrent: That can help you make a plan for readiness that's well-aligned with the This article offers a high-level view of typical development and testing phases Ready, performing as expected for users and ideally taking advantage of newįeatures and APIs to get the most out of the new platform. Released to AOSP (Android Open Source Project), it's important for apps to be Since users can start receiving the new platform as soon as the source code is While in other cases you might need to make changes to your app to adapt to the In many cases your app will work exactly as expected out of the box, With each release of Android, we introduce new features as well as behaviorĬhanges aimed at making the Android more helpful, more secure, and better
0 kommentar(er)
