[RFC] Raising Minimum Supported SDK from API 21 (Android 5.0) to API 23 (Android 6.0)
Summary
We are proposing to raise the minimum supported SDK (minSdkVersion) for Kodular apps and components from API 21 (Android 5.0 Lollipop) to API 23 (Android 6.0 Marshmallow).
Before making this transition, we want to share the rationale, review the global ecosystem data, and gather feedback from the developer community.
Market Stats & Device Distribution
According to data compiled on apilevels.com:
| Android Version | API Level | Release Year | Cumulative Global Usage |
|---|---|---|---|
| Android 5.0 (Lollipop) | API 21 | 2014 | ~99.8% |
| Android 5.1 (Lollipop_MR1) | API 22 | 2015 | ~98.2% |
| Android 6.0 (Marshmallow) | API 23 | 2015 | ~98.0% |
Raising the minimum SDK to API 23 means dropping support for roughly ~1.8% of active legacy devices globally, while ensuring Kodular-built apps remain accessible to 98.0% of all active Android users worldwide.
Why We Are Proposing This Change
- Ecosystem Deprecations: Standard dependencies across the Android ecosystem have discontinued support for API 21/22. Jetpack/AndroidX libraries require
minSdk 23+, and Google Play Services (v24.28+) requires API 23 or higher. - Modern Component Capabilities: Supporting API 21 holds back updates to core libraries (networking, media players, modern permissions/crypto APIs, and layout renderers).
- Builder Stability & Smaller Binaries: Eliminating legacy shims, multi-dex workarounds for Lollipop, and outdated fallback code will reduce APK size and improve build reliability.
- Security & Platform Standards: Android 5.x devices no longer receive security patches and lack modern TLS/SSL trust-store capabilities needed for secure network requests.
Impact on Creators & Existing Projects
- Existing Apps on Google Play: Existing published builds will continue working, but future app updates built on Kodular will target devices running Android 6.0 Marshmallow and above.
- Extension Developers: Extension developers will no longer need to write compatibility layers or maintain backwards compatibility for API 21/22.
We’d Love Your Feedback
- Do you have active deployments or enterprise clients strictly reliant on Android 5.0/5.1 devices?
- Are there specific components or extensions you maintain that would be impacted by this bump?
Please share your thoughts, concerns, and suggestions below!