ebelinski / apilevels Goto Github PK

August 2023 has passed and the table can be simplified based on that.

Hello, I found that the version code of Jellybean text is different from Build.VERSION_CODES

JELLY_BEAN, JELLY_BEAN_MR1, JELLY_BEAN_MR2 are exist in Build.VERSION_CODES, but the apilevels pages shows them as JELLYBEAN, JELLYBEAN_MR1, JELLYBEAN_MR2.

I think they needs to be changed to match the names in SDK.

Sources:

• https://android-developers.googleblog.com/2023/10/android-14-is-live-in-aosp.html
• https://arstechnica.com/gadgets/2023/10/android-14-officially-releases-for-pixel-phones/

https://developer.android.com/google/play/requirements/target-sdk

Starting in November 2021, app updates will be required to target API level 30 or above and adjust for behavioral changes in Android 11.

Wear OS apps must continue to target API level 28 or higher.

https://support.google.com/googleplay/android-developer/answer/9859152?visit_id=637837433771855271-4058277606&rd=1#targetsdk&zippy=%2Ctarget-api-level-requirements-for-play-console

Android 11 (API level 30)* | 2 August 2021: Required for new apps, 1 November 2021: Required for app updates

So

• tag API 28: as Wear OS minimum target.
• tag API 30: as Required App minimum target

Also 1.1 is Petit Four

I see the source of this data is statcounter, and they break down their data by region, US, UK, World, etc.

As a feature request, can the data be sliced by region?

On mobile browsers the table extends beyond the page boundaries and ruins the viewport width.

In the screenshot I did zoom out, the page starts zoomed in initially.

Would be better if the table scrolled horizontally on mobile displays.

It should be possible to create a github action to run one a week/month to download new data, and publish it, without human interaction.

Would this be useful?

It would be nice to have information about API 31, similar to what is there for API 33 and 34:

See:

https://support.google.com/googleplay/android-developer/answer/11926878?hl=en

App availability requirements

Currently, existing apps (...) must target API level 31 or above (...). Otherwise, they will stop being discoverable to all Google Play users whose devices run Android OS versions newer than your app’s target API level (...).

See https://developer.android.com/about/versions/12/12L/overview for details.

Hey, in the past I researched a similar project in the past, and got some more info:
https://docs.google.com/spreadsheets/d/1qOYY6km7TU6O6yBgUuDID6CQ5vox0rsWDrE_4Ikh28Y/edit?usp=sharing
Moved to Notion: https://twisterrob.notion.site/53fadafff3704e938266aa1fe1c93c92

I wonder if it would be useful to expand the site somehow with these?

https://android-developers.googleblog.com/2023/10/androidx-minsdkversion-19.html

https://developer.android.com/about/versions/14/behavior-changes-all#minimum-target-api-level

Android 13 has an internal codename already (Tiramisu) but it still feels a little early to add it to the site.

Information:

• Version: Android 13
• API level: 32
• Version code: T
• Codename: Tiramisu (internal)

Sources:

• https://www.xda-developers.com/google-android-13-t-tiramisu-dessert-name/

According to this story on xda, Android 10, 11, and 12 do have internal dessert names:

Android 10: Quince Tart
Android 11: Red Velvet Cake
Android 12: Snow Cone

where are you getting the year data?

Hi, thanks for the useful information about Android versioning.

It would be useful for me to know the latest (as well as earliest) NDK version that supports a given API level.

For example, ndk;23.1.7779620 seems to support android21 through android31.

I don't know how to get at this information without downloading each NDK with sdkmanager and manually checking the compilers available in ${ANDROID_HOME}/ndk/${NDK_VERSION} , which would be a lot of work for all the available NDKs.

What do you think?

I don't currently have a proposal for the implementation or design of this feature but it would be nice if we could add more information for other formfactors such as Wear OS, Automotive and Android TV since those platforms have different version names and requirements for target sdk.

Thoughts? I'm thinking about

• android.annotation.TargetApi https://developer.android.com/reference/android/annotation/TargetApi
• tools:targetApi https://developer.android.com/studio/write/tool-attributes#toolstargetapi
• androidx.annotation.RequiresApi
• androidx.annotation.ChecksSdkIntAtLeast
• androidx.test.filters.SdkSuppress
• Robolectric's Config

and what they do, in what practical cases they might be useful?

HTML is not good for progamming api level to platform version, it would be nice to have a better api to do so

Thanks for sharing!

This is a nice little page that could be useful in a PDF format, I've seen other cheat sheet websites offer a PDF link so it'd be great to have one here too.

A quick google search leads me to find that stuff like https://github.com/abemedia/jekyll-pdf exists which might be useful.