MOTODEV Studio vs. Android Google plugin [closed]

Question

Does anybody have any advice, experience, suggestions? I'm pretty comfortable with Google plugin - what would make me change to MOTODEV? Needless to say - I will download and play with it but I'm also interested in fellow developer's feedback.

Answer 1

I'm the product manager and tech lead for MOTODEV Studio, so let me jump in and try to help. Sorry about the delay, I wasn't aware any conversations about MOTODEV Studio were occurring on StackOVerflow. I'll make a point of following the conversations here as well.

MOTODEV Studio is a branded version of the IDE. It is not an RCP application. We integrate the Google ADT plugins into the Eclipse Core along with CVS, SVN, and Mylyn. You will need to add connectors for your specific backends if you use Mylyn as there are way to many choices for us to bundle all of them. We support Studio through our discussion boards at http://developer.motorola.com and if you visit, you won't see my teams' responses being "it works on my machine".

The next version of MOTODEV Studio comes out next week (~March 23). It will install as a single application and (despite what Fred suggests) you can also use the Eclipse update mechanism to install the Studio plugins into an existing Eclipse shell. We've also added support for 64-bit VMs on Windows, Mac, and Linux. Linux support is tested on Ubuntu and Fedora, but it may or may not work on others.

In addition to the Google ADT plugins, we add our own features, as DroidIn mentioned. Some of these you may find useful and others you may not. We're not in competition with Eclipse or Google on any of this--I and my team are committers and leaders on Eclipse OSS projects and we work with the Google tools team on joint efforts. If you like MOTODEV Studio, we'd love to hear from you and find ways to improve it. If it's not your cup of tea, that's fine, too. Let us know if there's anything we can do to change your mind.