Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search. I currently have a application targeted at android 2. So I thought that using api level 3 would be the best to use, but I don't know if this will maybe make certain elements in my app work less good, and probably buggier, since it actually uses old android code.
Is there a good way to find out which API level I should use, and also, how do I convert my application to that level? You can find a breakdown of the different versions of Android in use here.
Currently, if you target 2. Targeting 2. As for converting your app, you can check what API level things are available for in the Android Reference. You'll note a checkbox and dropdown menu on the top right of the browsing area that allows you to filter by API level - that's one way to help converting.
The other is to set the target and minimum SDK versions which will help Eclipse know what to complain about in your code. The easiest way to see if something needs conversion, however, is to emulate and test. This graph may help you make up your mind. It is good to look at backward compatibility and in general, you should compile your application against the lowest possible version of the platform that your application can support.
You can determine the lowest possible platform version by compiling the application against successively lower build targets. After you determine the lowest version, you should create an AVD using the corresponding platform version and API Level and fully test your application.
Make sure to declare a android:minSdkVersion attribute in the application's manifest and set its value to the API Level of the platform version.
Good luck! Revision 1 August Initial release for Android 7. Android SDK Tools Android 6. Revision 2 November Fixed bugs in the layout rendering library used by Android Studio. Revision 1 August Initial release for Android 6. Android 5. Revision 1 March Initial release for Android 5. Revision 2 December Updated layouts in the Support Library and fixed various issues.
Revision 1 October Initial release for Android 5. Android 4. Revision 2 October Updated the rendering library. Revision 1 June Initial release for Android Wear. Revision 2 December Maintenance release.
Revision 1 October Initial release. Revision 2 August Maintenance update. Revision 1 July Initial release. Revision 2 February Maintenance update. Dependencies: SDK Tools r21 or higher is required. Revision 1 November Initial release. Dependencies: SDK Tools r20 or higher is required. Revision 3 October Maintenance update.
Revision 2 July Maintenance update. Revision 1 June Initial release. Revision 2 January Maintenance update. Dependencies: SDK Tools r14 or higher is required. Revision 1 December Initial release. The following considerations apply to apps targeting Android 8.
For an exhaustive list of changes introduced in Android 8. For an exhaustive list of changes introduced in Android 9. Continue to update to API 30 by following the instructions in the previous section. As you update the target API level for your apps, consider adopting recent platform features to modernize your apps and delight your users.
You should also verify any restrictions that may exist in the version of the Android Support Library that you're using. We encourage you to update to a recent compatible Support Library in order to take advantage of the latest compatibility features and bug fixes.
After you update your app's API level and features as appropriate, you should test some core use cases. The following suggestions are not exhaustive, but aim to guide your testing process. We suggest testing:. Handles Doze with expected results and no errors. Using adb, place your test device into Doze while your app is running. Test any use cases that trigger Firebase Cloud Messaging messages.
Test any use cases that use Alarms or Jobs. Eliminate any dependencies on background services. Test any use cases that use Alarms. Ensure that any critical use cases that depend on these events still work. Opt in to emails in the Google Play Console so that we can send you important updates and announcements from Android and Google Play, including our monthly partner newsletter.
Content and code samples on this page are subject to the licenses described in the Content License. Google Play. Expansion files OBBs will no longer be supported for new apps. Why target newer SDKs? Migrate from Android 10 API level 29 to Android 11 API level 30 Privacy Scoped storage enforcement : Apps should adopt the scoped storage model where app-specific, media, and other file types are saved and accessed using dedicated locations.
Permissions auto-reset : If users haven't interacted with an app for a few months, the system auto-resets the app's sensitive permissions. This shouldn't affect most apps. If your app primarily works in the background without user interactions, you may consider requesting users to disable auto reset.
0コメント