Google's Android Studio Is Built on IntelliJ IDEA Community Edition

Every Android developer who has opened Android Studio has been using a JetBrains product without necessarily knowing it. The official Android IDE is not written from scratch by Google. It is a fork of IntelliJ IDEA Community Edition, the open source edition that JetBrains released under the Apache 2.0 license in December 2009, extended with Android specific plugins, build integration, and device tooling.

The background explains why Google took that route. Before 2013, Android development ran on Eclipse with the ADT plugin, a combination that worked but aged badly. Project configuration was scattered across manifest files and plugin settings, the XML layout editor was rudimentary, and refactoring a large Android codebase in Eclipse was painful. IntelliJ IDEA by contrast had been shipping since January 2001 and had built its reputation on code navigation and automated refactoring, the two things that matter most once a codebase stops fitting in your head.

Google announced Android Studio on May 16, 2013 at the I/O conference. The pitch was straightforward: take the IntelliJ platform, build the Android tooling on top of it, and standardize on Gradle for builds. The first stable release did not arrive until December 2014, with version 1.0, and by the end of 2015 Google had dropped support for Eclipse ADT entirely. The migration was not gentle for teams with long lived Eclipse setups, but the direction was unambiguous.

What makes this more than trivia is the architecture beneath it. The IntelliJ platform is a general purpose IDE framework with a program structure interface that models source code as a tree, persistent indexes that make cross project search fast, an inspection engine that flags problems as you type, and a plugin API that other tools build against. Android Studio is essentially the platform plus the Android plugin, which contributes Gradle synchronization, the resource and layout editors, the APK analyzer, the emulator controls, and the profilers. That is why keyboard shortcuts, refactoring dialogs, version control integration, and the settings layout feel identical in Android Studio and in IntelliJ IDEA.

The practical consequences show up daily. Because the Android plugin is a plugin, the platform's other strengths come along for free: structural search, language injection, database tools in the ultimate edition, and hundreds of third party plugins. Because the build system is Gradle, the IDE does not own your build logic, which means continuous integration runs the same tasks the IDE runs. And because everything is JVM based, Android Studio inherits the platform's appetite for memory. The familiar pause while indexes rebuild after a branch switch, and the need to raise the heap size on large projects, are the price of that indexing model.

There is a strategic lesson here for anyone designing tools. Google could have written a new IDE. Instead it adopted a mature platform and spent its effort on the parts that were genuinely Android specific. That decision compressed years of work into a single release cycle and gave Android developers an editor whose core had already survived a decade of production use in the Java world. The tradeoff was dependency on an external codebase and an external company, which is a familiar tension in platform engineering: build versus adopt, and how much control you are willing to trade for speed.

It also reshaped JetBrains' business in a way few predicted. Having the most popular mobile IDE in the world built on their platform validated the IntelliJ architecture and pushed the company's tools into millions of machines that would never have installed a Java IDE. The same platform now underlies PyCharm, WebStorm, PhpStorm, GoLand, Rider, and the unified IntelliJ IDEA release, and Kotlin, JetBrains' own language, became a first class Android language in 2017.

So the next time Android Studio finishes a Gradle sync and offers a rename refactor across twenty files, remember that the intelligence doing the work was designed for Java development in Prague at the turn of the century. The Android part is the plugin. The IDE underneath is older, more general, and considerably more ambitious than the mobile platform it ended up serving.