![]() ![]() Coincidentally, android tends to support only the top 80% of API levels, so that could be another metric for the 80/20 maxim. My minSdkVersion is now 28, which still covers the top 78.4% of android versions according to apilevels. I found this out the hard way starting out. In this case, 80% of the issues (and potential 1 star ratings) come from the bottom 20% of android API levels. I use the Pareto Principle, that roughly 80% of consequences come from 20% of causes, in determining the percentage of devices to support. Keep in mind that prior to rev 23, the most recent version was 22.6. Then just download the SDK you need after installing the ADT Version that you want. Android Studio Chart - ObsoleteĪ - Current as of on this writing Jan 23 See this answer for getting earlier versions of the Android ADT plugin for Eclipse. The latter appears to give the most current numbers. Websites with current use version info include, , and. Also similar to the old dashboard chart, it is terribly obsolete. Before you can configure an API level for your project, you must install the SDK platform components for that API level. This API level is used at run time by Android. First off, when you create a new project, on the screen where you enter your minimum sdk among other items there is a 'help me choose' link which will bring you to a list of android version use percentages, info similar to that given in the old dashboard pie chart. Target Android Version Specifies the version of Android that your app is intended to run on. As the Google dashboards page has stopped giving version percentages for some time, years to my memory, I thought I'd give an updated answer to this salient issue. Android Mobile Messaging SDK version 5.17.0 release includes new features, enhancements and bug fixes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |