Move fast, break all the tutorials.
Android has a problem with churn in tooling.
Long time eclipse user, impossible to go back after using android studio. It feels like programming with one hand tied behind my back.
I switched to Studio 2.0 hoping for better NDK support over 1.5.
However, it appears to still require the experimental Gradle plug-in. Which, frankly, isn't very good.
I'm still building my native .so separately using NDK build. I don't get any native code debugging either.
Is there something obvious I'm missing?
Does anyone ever actually experience greater emulator performance under Windows? Each time an update is pushed, I am excited to always see "XX faster emulator" listed as an improvement - but never do I see a notable improvement... So far, the only usable "emulator" that I've found is actually virtualization using Xamarin's Android Player...
What's wrong with a sane makefile oriented thing with a small tool chain and letting the user pick the editor/IDE? Why does every large company build out this ridiculous IDE for their product?
I need to upgrade, the amount of random steps I had to take to make the old AS even remotely manageable was a headache.
Why's it so hard just to get adb these days? My adb requires like 5gb of other stuff
And it is still slower than good old Eclipse.
So, how to enable material design?
Maybe this is better left as a comment SO, but we have been unable to any recent version of Android Studio for our development team for the past four months because we use a mapFragment in our app. It's a known error [0] in the Maps API v2. I understand the complexity Google is facing, but I can't imagine Apple not addressing such a fundamental UI capability in their dev tools. Frustrating.
[0] https://code.google.com/p/gmaps-api-issues/issues/detail?id=...