Skip to main content

Android Studio Release Updates

JetBrains's Android Studio’s 10 year anniversary

    I remember the major change which has taken place since I started learning android is Android Studio migration from Eclipse. Android Studio’s 10 year anniversary.


Watch official youtube : Android Studio’s 10th birthday: our favorite moments!


    In December 2014, Google launched Android Studio, Google's official Integrated Development Environment (IDE) based on IntelliJ and it discontinued the Android Developer Tools (ADT) plugin for Eclipse, which means it’s time to leave eclipse behind. 


    Fortunately, we had simple solution to migrate, Android Studio offered a better experience for Android developers and its migration functionality does most of the work for you.


    Open Android Studio and click on the option: Import project (Eclipse ADT, Gradle, etc)


Before Android studio


    1. users had to go download a JDK, then download Eclipse, then configure it with an update center to point to Android, install the Eclipse plugin for Android, and then configure that plugin to point to an Android SDK install.


    2. User has to build it on top of an actively maintained, open-sourced, and best-of-breed Java programing language IDE. Not too long before releasing Android Studio, we had all used IntelliJ and felt it was superior from a code editing perspective.


    3. User has to not only provide a build system that was better suited for Android app development, but to also enable this build system to work consistently from both from the command line and from inside the IDE. This was important because in the previous tool chain, we found that there were discrepancies in behaviour and capability between the in-IDE builds with Eclipse, and CI builds with Ant.


This led to the release of Android Studio, including these highlights:

First android Studio

JetBrains

“Google choosing IntelliJ as the platform to build Android Studio was a very exciting moment for us at JetBrains. It allowed us to strengthen and build on the platform even further, and paved the way for further collaboration in other projects such as Kotlin.” 

 – Hadi Hariri, VP of Program Management at JetBrains

Gradle

“Android Studio's 10th anniversary marks a decade of incredible progress for Android developers. We are proud that Gradle Build Tool has continued to be a foundational part of the Android toolchain, enabling millions of Android developers to build their apps faster, more elegantly, and at scale.”

 – Hans Dockter, creator of Gradle Build Tool and CEO/Founder of Gradle Inc.

“Our long-standing strategic partnership with Google and our mutual commitment to improving the developer experience continues to impact millions of developers. We look forward to continuing that journey for many years to come.” 

 – Piotr Jagielski, VP of Engineering, Gradle Build Tool

Android Studio was announced on May 16, 2013, at the Google I/O conference. It was in early access preview stage starting from version 0.1 in May 2013, then entered beta stage starting from version 0.8 which was released in June 2014. The first stable build was released in December 2014, starting from version 1.0.


The following features are provided in the current stable version:

  • Gradle-based build support
  • Android-specific refactoring and quick fixes
  • Lint tools to catch performance, usability, version compatibility and other problems
  • ProGuard integration and app-signing capabilities
  • Template-based wizards to create common Android designs and components
  • A rich layout editor that allows users to drag-and-drop UI components, option to preview layouts on multiple screen configurations.
  • Support for building Android Wear apps
  • Android automative. 
  • Android Television.
  • Built-in support for Google Cloud Platform, enabling integration with Firebase Cloud Messaging (Earlier 'Google Cloud Messaging') and Google App Engine.
  • Android Virtual Device (Emulator) to run and debug apps in the Android studio.    

When you open android studio today 

Android Studio supports all the same programming languages of IntelliJ (and CLion) e.g. JavaC++, and more with extensions, such as Go.

Android Studio 3.0 or later supports Kotlin, and "Android Studio includes support for using a number of Java 11+ APIs without requiring a minimum API level for your app". 

External projects backport some Java 9 features. 

While IntelliJ states that Android Studio supports all released Java versions.


The first stable release of Android Studio was version 1.0


Below list shows list of android studio versions came before Gemini.


Version

Release date

1.0

December 2014

1.1

February 2015

1.2

April 2015

1.3

July 2015

1.4

September 2015

1.5

November 2015

2.0

April 2016

2.1

April 2016

2.2

September 2016

2.3

March 2017

3.0

October 2017

3.1

March 2018

3.2

September 2018

3.3

January 2019

3.4

April 2019

3.5

August 2019

3.6

February 2020

4.0

May 2020

4.1

Oct 2020

4.2

May 2021

Arctic Fox (2020.3.1)

July 2021

Bumblebee (2021.1.1)

January 2022

Chipmunk (2021.2.1)

May 2022

Dolphin (2021.3.1)

September 2022

Electric Eel (2022.1.1)

January 2023

Flamingo (2022.2.1)

April 2023

Giraffe (2022.3.1)

July 2023

Hedgehog (2023.1.1)

November 2023

Iguana (2023.2.1)

February 2024

Jellyfish (2023.3.1)

April 2024

Koala (2024.1.1)

June 2024

Koala Feature Drop (2024.1.2)

August 2024

Ladybug (2024.2.1)

September 2024

Meerkat (2024.3.1)

In Preview version



Refernce:


https://developer.android.com/studio/releases


https://en.wikipedia.org/wiki/Android_Studio


https://android-developers.googleblog.com/2025/01/android-studios-10-year-anniversary.html

Comments

Popular posts from this blog

Google re-branded the support Android libraries to AndroidX

It is important to note, you cannot mix AppCompat and Jetpack in the same project. You must convert everything to use Jetpack if you want to upgrade. The support library artifacts are being deprecated and all future development is going into AndroidX , so there's no avoiding this migration. Alan Viverette sums this up nicely: “There won’t be a 29.0.0, so Android Q APIs will only be in AndroidX” The stable release of 28.0.0 will be the final feature release packaged as android.support . All subsequent feature releases will only be made available as androidx-packaged artifacts. Below tips will give you a clearer transition path. The current version of AppCompat (v28.x) is exactly the same as AndroidX (v1.x). In fact, the AppCompat libraries are machine generated by changing maven coordinates and package names of the AndroidX codebase. For example, android.support.v7.app.AppCompatActivity is now androidx.appcompat.app.AppCompatActivity For a complete listi...

Android Beginners Guide

                                                                                                               Android Operation System: Android is an operating system based on Linux with a Java programming interface. It provides tools, e.g. a compiler, debugger and a device emulator as well as its own Java Virtual machine (Dalvik Virtual Machine - DVM). Android is created by the Open Handset Alliance which is lead by Google. Android uses a special virtual machine, e.g. the Dalvik Virtual Machine. Dalvik uses special bytecode. Therefore you cannot run standard Java bytecode on Android. Android provides a tool "dx" which allows to convert Java Class files into "dex" (Dalvik Executable) files. Android ...

Android Pi migration(28 API support)

I am here to give some inputs on android PI migration. .  Apps must target at least API level 28 to ensure it is built on the latest APIs optimized for security and performance . From August 2019, new apps must target at least Android 9.0 (API level 28) . The objective here is to make sure that your existing app works as-is on Android 9. Because some platform changes might affect the way your app behaves, some adjustments might be necessary, but you do not need to use new APIs or change your targetSdkVersion. Android Service Problem On Oreo, startService() will throw IllegalStateException. This can be fixed by changing it to startForegroundService(). but it also stops the service immediately if you don’t bind to the Notification with Service.startForeground() within 5 seconds. For other background service we decided to use the WorkManager . Implementation: Since we have minSdkVersion 19, We migrated to workmanger for scheduled tasks and we still use JobInten...