Android Studio vs Eclipse with ADT (2015) [closed]

Question

As of 2015, I see that Android studio is an official IDE for developing android applications according to information on their official site and on each page of their site, there is a note suggesting to go for Android studio rather than Eclipse with ADT.

Note: If you have been using Eclipse with ADT, be aware that Android Studio is now the official IDE for Android, so you should migrate to Android Studio to receive all the latest IDE updates.

But I haven't found any latest article about the pros and cons in choosing the IDE or eclipse with ADT. If some one can throw some light on it then it would help other beginners like me in choosing the right app for android development

Answer 1

Eclipse is far more superior to AS. It is much easier to use, more intuitive, much less buggy (even though alot buggier than VISUAL Studio, but we're comparing to AS), and will probably make your work more productive. It's 2016 now and I'm planning to keep using Eclipse as long as it's possible.

Answer 2

For Android development definitely Android Studio is better than Eclipse. I have worked on Eclipse for almost 4 years but when I switched to Android Studio, I felt the difference. Below are few points I have noticed:

Performance: Android Studio's performance is better than Eclipse and improving with each new release.

Intelligent: Android Studio is more intelligent than Eclipse. It gives you suggestions more accurate and fast

More options: You can build multi flavor APKs at once in build.gradle

Summary: After working on Android Studio if you will work on Eclipse you will feel the same as driving a entry level car of Toyota after driving Lamborghini Aventador :) I felt this difference

Update:

Android Studio 2.0 is coming. Its very very fast than current Android Studio. http://android-developers.blogspot.jp/2015/11/android-studio-20-preview.html

Update:

Android Studio 3.0 is released. As I mentioned 2 years ago about the difference, Android Studio is getting better day by day. Have a look into AS 3.0 : https://android-developers.googleblog.com/2017/10/android-studio-30.html

Answer 3

I am new and I started with AS, but soon grew frustrated when it came down to using other developers repositories in my project. The whole aggrevating process and guesswork of migrating them over to the gradle and configuring manually just became over bearing to me, so I went retroactive and downloaded Mars1 and gave it a try. I found it to be a little unintuitive at first, but once it I learned the navigation I fell in love with the openness of it.. I still intend to use Android Studio for all or my releases, but eclipse is now my goto ide right now unless Google tries making some API that is only used in Studio. I like options and hate it when companies try to streamline they lose great experienced developers that way. Also @mistersmith...you probably cannot afford to be that naive. You are going to go the way of the dodo thinking their is only one solution and feeding into corporate garbage. You may not know it, but google is grooming people like you into believing AS is the only practical solution. Just wait until you are forced to migrate to something differnent in the future after buying into AS for all of your mobile application needs.