Android Studio uses the quick growing Gradle build system that is so integrated, and Gradle is really a great tool. If you have decided to go with Eclipse than yet say to look at Gradle’s features and try it out and see if it fits with your project. In case you want to go with Android Studio, no need to worry about being stuck with Gradle system because it is really good.
Android Studio tend to get me where we want to be a little more promptly and effortlessly than their counterparts in Eclipse. In addition, AS was built purposely for Android, while Eclipse was built to all-purpose IDE that can be used with any language and platform.
Android Studio is now released with very less bugs, and provides a more stable performance guarantee than Eclipse and the system needs are lower too. AS is quick, while you need 1 or 2 minutes for building release versions of complex projects in Eclipse, but can make the same project within 30 seconds in AS.
Both Android Studio and Eclipse feature the typical Java code auto completion. But, we usually found that the code completion is really better on AS compare to Eclipse which looks to get a bit perplexed at times and doesn’t provide precise results most of the time. Keep in mind, the more time you will spend as a programmer grinding out code, the more you value code completion.
Android Studio uses modules to manage and organize your code modules have their own Gradle build files which mean it can state their own dependencies. In compare AS looks more natural, but if you have been using Eclipse for some time, then it takes a little bit time to get used to.
Android Studio has GUI (Graphical User Interface), but Eclipse does not have. However, the drag-and-drop feature is not essential for coders, who are not very much concerned regarding the visual elements of their applications. A developer needs to have detailed knowledge of Visual Basic.