Getting students up and running with Android Studio seems similar to trying to teach HTML+CSS+JS, by having students start with Grunt/Gulp + WebPack/NPM + Ember + Bootstrap and more.
We don't usually do that, because it's a crazy amount of complexity for someone just starting out. Most students begin with something like "edit a single HTML file to learn basic HTML+CSS+JS", and get gracefully introduced to the rest as they learn.
I imagine we need an equivalent of that for Android. I don't know what specifically that would be, but it's probably not Android Studio.
PS FRC was my life for 2005-2009... great memories, an incredible program. Definitely instrumental in getting me to where I am today. :)
http://www.firstinspires.org/robotics/ftc
If so, what a seriously amazing group....if not, I'll update the link!
Couldn't agree with you more.
Point 4 - Remote Debugging is an especially important one. Not only not having to connect using the cable but saving the tremendous amount of wear and tear on the phone USB connector. This is usually a big factor in robot failure due to loose connections during a competition. Thank God for inventing Duct Tape.
If I didn't personally use Android Studio before it would have been a huge hurdle to teach my team to use it. Too many moving parts, the android ecosystem and the wide variety of SDKs and tooling. What would be considered as a great selling point otherwise is a burden to get setup for a bunch of middle and high schoolers.
1 - The author is right: The WYSIWYG GUI tools are buggy as hell and I have just have the kids dive into the XML - which brings its own set up problems.
2 - The gradle system is hard to configure but once it is right and you check in the configs you don't need to change it.
3 - It basically requires 8GB to run with any reasonable performance. Getting a set of laptops with 8GB for a non-profit is a challenge! Even with 8GB, build and deploy cycle can take 3 - 5 minutes.
4 - I do like the remote debugging. It is essential for debugging a robot with a phone that is driving around on the floor.
Android 2.0 was an improvement, but it is still a challenging environment.
I am a competent programmer who uses IntelliJ at work, so I don't know how other FTC coaches could possibly get a team up and running with Android Studio.