I don't know if the 16GB version performs any better, too. I had 5 Macbooks in total and I was really happy with them, so I really want that this one provers is value too. I spent a lot of money (living in Brazil) and it has not been a good investment. The M1 is not good for Android Development yet. My conclusion is: Don't expect Google fixing the problems soon. Tried to build a small Compose project in AS but I spent more than 1 hour just to build a 'Hello World'. A lot of times the code completion is gone, Gradle builds fails and references vanish away randomly. It works, but it works bad on the 8GB version. IntelliJ worked kinda fine, but the ARM Android Emulator sucks more than 50% of my RAM. So, I downloaded the latest IntelliJ EAP. Then, Android Studio showed that it's not possible to work with it in Rosetta's emulation. Then I found that the workaround was adding the latest Xerial's version of SQLite JDBC. Neither going to tell the already common-sense stuff, such as using Azul's JDK and the need to use the Canary versions of AS ou IntelliJ.Īt first, I had problems to run projects that were dependent on SQLite.

I am not going to talk about battery, browsing and watching videos experience, just the Android developer experience. I will be dedicating my time to express my experience with Android Development in almost a month that I have been working with a MBP 8GB/256GB.

Android studio mac m1