Google makes Android Studio 3.0 preview available for download; 20+ new features include performance profiling tools, Instant Apps, Java 8, and Kotlin
At its I/O 2017 developer conference, Google today unveiled Android Studio 3.0, the latest version of its integrated development environment (IDE).
Context & Ripple Effects
This preview continues a steady tooling cadence Google has run since Android Studio 2.0 brought Instant Run and a faster emulator in late 2015, then stabilized in April 2016. The 3.0 preview bundles four levers at once — performance profiling, Instant Apps, Java 8, and Kotlin — making it less a routine IDE bump than a statement about how Google wants Android apps built.
The Kotlin inclusion is the notable one: putting the language inside the official IDE gives it distribution no third-party tooling could match, and Google's later dedicated Kotlin language release for Android developers confirms the bet stuck.
First-order effects
- Android developers testing the preview immediately gain built-in performance profilers and Instant Apps support, removing the need to assemble those workflows from separate tools.
- Kotlin becomes a first-class citizen of Google's own IDE, shifting it from community-favored alternative to officially supported Android language overnight.
Second-order effects
- Tooling vendors building profilers and Java 8 workarounds for Android now compete against features shipping free in the default IDE, pressuring them toward capabilities Google doesn't bundle.
- Teams planning app architecture face a concrete decision point on Kotlin adoption, since the language's IDE integration lowers switching costs ahead of the stable 3.0 release.
Third-order effects
- The cadence itself — 2.0, this 3.0 preview, then Android Studio 3.2 with App Bundles and eventually 4.0's Motion Editor — shows Google using its IDE as the delivery mechanism for platform policy, from build formats to animation tooling.
- If bundling languages into the official toolchain keeps working, Android development consolidates around Google-chosen defaults, with language and format decisions made in Mountain View rather than by ecosystem consensus.
The trend: Google is turning Android Studio into an annual-cadence lever for steering how Android apps are written, packaging language choices like Kotlin directly into the default toolchain.