Android SDK Release Update
Article Summary
Matthew McCullough just dropped a bombshell: Android is ditching its annual release cycle. If you're building for Android, your entire 2025 planning timeline just changed.
Matthew McCullough, VP of Product Management for Android Developer, announces a major shift in Android's release strategy. Starting in 2025, Android will move from one annual SDK release to multiple releases per year, fundamentally changing how developers plan their app updates and compatibility testing.
Key Takeaways
- Two SDK releases in 2025: major Q2 release, minor Q4 release with new APIs
- Q2 major release moves up from Q3 to align with device launches
- Minor releases won't increment API level, use new minor API level constant instead
- Only one annual targetSdkVersion requirement tied to major API level
- Meta improved targetSdkVersion adoption velocity by 4x using this approach
Android's new multi-release strategy aims to accelerate innovation while maintaining stability, but developers need to shift compatibility testing earlier in the year.
About This Article
Android developers had to deal with unpredictable release cycles. The annual SDK updates meant compatibility testing happened late in the year, right when device launches were already happening. This created a mismatch between when the platform was ready and when the ecosystem needed it.
Google changed the 2025 release calendar to add Q1 and Q3 incremental updates alongside major and minor releases. They introduced a minor API level constant and manifest attribute so developers can target specific SDK versions without needing to run full behavior change testing.
Developers can now test builds against major and minor API levels separately. This cuts down the work needed for compatibility testing on minor releases. Google can also ship new developer APIs four times a year instead of once, which means features get out to the Android ecosystem faster.