AndroidDevelopment

Google released the stable build of Android 17 on 16 June 2026, with Pixel 6 and newer phones receiving it from 17 June. It is API level 37 and the first release under Google's new cadence: one major SDK release in Q2 and a minor SDK release in Q4. Platform stability was reached with Beta 3 on 26 March 2026, so most teams had almost twelve weeks of a frozen API before launch.

Changes that affect existing apps

• For apps targeting API 37, orientation and resizability restrictions are ignored on large-screen devices, and developers can no longer opt out. Phone-only layouts will stretch on tablets and foldables.
• Per-app memory limits are now tied to device RAM, so memory-hungry apps may be killed sooner on low-end devices.
• Vulkan 1.4 support and mandatory ANGLE on new devices change the graphics baseline for games and media apps.
• Versatile Video Coding (H.266) support brings similar or better video quality at smaller file sizes.
• Stricter PIN and password attempt limits, plus a privacy-preserving Contacts Picker.

Release timeline

User-facing additions

Bubbles floating windows, 90:10 split-screen ratios, Continue On task handoff between Android devices and Gemini-driven Device Help round out the release. The headline Gemini features require recent flagship hardware.

Why this matters: the large-screen rule is a hard change. Apps with locked portrait layouts will look broken on tablets and foldables once they target API 37.

Businesses that hire Android developers on a short engagement often use news like this to decide what to tackle first.

Is your Android app adaptive yet? Nestack's outsourced Android teams migrate apps to API 37, Compose adaptive layouts and the new memory rules.

JetBrains shipped Kotlin 2.4.0 on 14 July 2026 and the follow-up Kotlin 2.4.20 on 7 September 2026. Both are already bundled in current Android Studio builds, so most Android teams will meet them in the next dependency update.

Language and library changes in 2.4.0

• Context parameters, explicit backing fields and the new annotation use-site targets (including the @all meta-target) are now stable.
• A stable UUID API in the common standard library, plus isSorted()-style checks and null-aware map helpers.
• Experimental collection literals using bracket syntax and richer compile-time constants.
• Support for Java 26 on the JVM.

Build changes you must plan for

• The K1 compiler is gone: language version 1.9 is no longer accepted.
• Minimum Android Gradle Plugin is now 8.5.2; Gradle 7.6.3 to 9.5.0 is supported.
• Kotlin/Native switches the CMS garbage collector on by default and supports Xcode 26.4, relevant to teams sharing code with iOS.

What 2.4.20 adds

The September release focuses on tooling: coroutine stack-trace recovery, allDistinct() and allEqual() collection checks, lazy messages in kotlin.test, an experimental native image of kotlinc for faster startup, and Swift export support for sealed classes with automatic Package.swift generation. The watchosArm32 target is deprecated ahead of Kotlin 2.5.0, which reached Beta 2 on 21 October 2026.

Date for the diary

KotlinConf 2027 runs 21 to 23 April 2027 at the ICE Krakow Congress Centre in Kraków, Poland, with workshops on the first day. The call for speakers closes on 27 November 2026.

Why this matters: removing K1 and raising the AGP floor means older Android projects need a deliberate upgrade step before they can take any new Kotlin features.

This is usually the moment businesses hire Android developers to review their options and the cost of staying behind.

Need help upgrading an Android codebase to Kotlin 2.4? Nestack's Android engineers handle compiler, Gradle and Compose migrations without disrupting releases.