

They all seem a bit minor, with the exception of the JetPack Navigation component editor.
#Android studio 3.3 android
So what does the pain Android Studio 3.3 has given me get me in return? My best guess is that I'm not the only one who will hit difficulties - although I'm not saying that there aren't some users who will have a better experience. The problem is that I'm a sample of one and so you can't really generalize, but breaking existing projects and not making the upgrades necessary clear has a long history in Android Studio updates. At first this too failed with a broken pipe error but on a second attempt it did work.

So given I needed to find some things out about Studio 3.3, I gave up and started a new project. My old Java projects similarly failed to build.
#Android studio 3.3 upgrade
Eventually I did get some information that made me upgrade the SDK and later Gradle and much later the Kotlin add-in - but I still couldn't make my old projects work. My Kotlin-based projects loaded and hung forever while building.

Everything seemed to be working and then I tried loading and working with some existing projects. In installed nicely and even offered to delete redundant IDE folders - but disk space isn't really an issue. I have to say that I started out with the new version with a lot of hope. Every time they tweak an aspect of the UI, users have to do battle to get back to where they where. For me this is the biggest indicator that the Android Studio team really don't seem to understand that they have users. Yes, the spinners and other widgets that disappeared when Android Studio 3.1 was released are still missing. Project Marble is the Android Studio team's way of trying to focus on code quality and Android Studio 3.3 has had 200 user reported bugs cleared up - but not mine. I really wanted to like this one but, as with other recent upgrades, it introduces a lot of churn and my existing projects won't work with it. Another decimal point upgrade to Android Studio and more hope for the future.
