Well, as ready as any of the recent Android Studio's have been. This one boasts an AI assistant called Gemini - shame Android Studio isn't as fast to implement as Gemini is to suggest.

You need to know that, while initially I was an enthusiastic Android developer, latterly I have become a critic of Android Studio and Android development as a whole - so you may not agree with my viewpoint. Personally I would have preferred that, for the latest release, the Studio team worked on making it more logical, less bloated and much faster. I installed it on the development machine I used a few years ago and discovered it was too slow to be workable - even though I could ask Gemini questions and get answers back quickly. It is a strange world where AI is faster than the toolset.

So what is new?

• Granular login permissions allow you to tailor who has access to what.
• You can now access Android Device Streaming to install your app and interact with the device. It doesn't work on all devices but when it does it is an easier way to test things.
• We now have better crash reports
• The layout inspector is embedded by default and it is 50% faster.

Of these only Android Device Streaming seems like a big improvement and this is another example of Android becoming a Google services platform rather than an App platform. As time goes by Android is more Google and less open source.

OK, so the most prominent improvement is Gemini, formerly called Studio Bot, so how could I not ask it the important questions:

1. Should I use Constraint Layout or Compose?
   The answer was, for new projects use Compose and to support older devices use Layout. It went on to say: "Ultimately, the best way to decide is to experiment with both Compose and layout managers and see which one works best for you."
   Right, it clearly has no idea how long it takes to master either.
   
   
2. Is it still good to use fragments?
   Overall, fragments are a powerful tool that can be used to create modular and reusable UI components. However, they should be used judiciously, as they can also add complexity and performance overhead to your application. But it then suggests:
   If you are unsure whether or not to use fragments, it is always a good idea to start with a traditional layout. You can always add fragments later if you need more flexibility or modularity.
   
   
3. Does the drag-and-drop editor have a future?
   Overall, the drag-and-drop editor has a bright future. It is a powerful tool that can be used to create modular and reusable UI components. However, it is important to be aware of the limitations of drag-and-drop editors and to use them judiciously.

Full marks for fence sitting.

Take a look at the launch video for a more positive viewpoint:

There are so many missing features of "old" Android Studio that I resent the time the team is spending on the "MAD" Android Studio, and vice versa.

• Mike James is the author of Android Programming in Kotlin: Starting With An App and Android Programming In Java: Starting With An App, 3nd Ed covering Android Studio 3.

More Information

Gemini in Android Studio and more: Android Studio Jellyfish is Stable!

Related Articles

Android Studio Hedgehog Is Now Stable

Android Studio Flamingo Improves UI Tools

Android Studio Electric Eel Released

Android Studio Chipmunk - Cute But Increasingly Unfit For Purpose

Android Studio Bumblebee Adds Support For ADB Over WiFi

Android Studio 4.2 Released

Android Studio 4.1 - No Relief In Sight

Android Studio 4 - Not One Giant Leap For Android Programming

To be informed about new articles on I Programmer, sign up for our weekly newsletter, subscribe to the RSS feed and follow us on Twitter, Facebook or Linkedin.

Comments

Make a Comment or View Existing Comments Using Disqus

or email your comment to: comments@i-programmer.info