When comparing Eclipse Che vs Android Studio, the Slant community recommends Android Studio for most people. In the question“What are the best IDEs for Android development?” Android Studio is ranked 2nd while Eclipse Che is ranked 9th. The most important reason people chose Android Studio is:
Android Studio is the software built by Google themselves to be used for Android Development. As such, it's certain that support for it will never drop as long as Android apps are still being developed. Studio is also the tool that Google recommends using for Android development and it's the IDE that gets updates related to Android first.
Ranked in these QuestionsQuestion Ranking
Pro Docker runtimes
Pro SSH + terminal
Built-in terminal with root access so you can make changes to your running machines. Being able to SSH into the workspace so you can use a desktop IDE is handy.
Pro GIT and SVN VCS support
Projects can be easily imported from any Git or Svn repository hosting service.
Pro Reproducible environment
Pro Custom commands
You can package up custom commands with your workspace and then use them (or share them) with everyone else.
Pro Portable workspaces
The workspace in Che includes project sources, IDE and the runtime. So if you hand your Che workspace definition to another user and they execute it they will get everything they need to build, run and debug the project.
Also the runtime is in a Docker container so it will work even if the second user is on a different OS than the original user who shared their workspace with them.
Che does a nice job to automatically map the service:port running in the Docker container (e.g. tomcat on 8080) to the Docker port it actually uses (something in the ephemeral range). You never need to figure that out - it's just made available when you run your server.
Pro Merge tool for VCS
Pro Officially supported by Google
Android Studio is the software built by Google themselves to be used for Android Development. As such, it's certain that support for it will never drop as long as Android apps are still being developed.
Studio is also the tool that Google recommends using for Android development and it's the IDE that gets updates related to Android first.
Pro Live code updates and renderings of app
Layouts are built and can be observed in real time and are automatically updated after every change. You can even see these changes on different screens.
Pro Based on the powerful IntelliJ IDEA
Unlike its predecessor, which is based off Eclipse, Android Studio is build on top of Jetbrain's Flagship Java IDE which offers over a number of features. It's also open-source too (Community Edition only).
Pro Uses the powerful Gradle build tool out of the box
Android Studio uses Gradle as the official build tool for projects, moving away from the now outdated Apache Ant.
Gradle is a powerful build tool, especially for Android development with which it's very easy to do things that are otherwise impossible or very hard to do on other build systems, thing like: upgrading the build system without breaking the project itself or allowing you to separately define the development and production versions.
Pro Intelligently replaces values
References are automatically replaced with their real values, so you can easily view which color you are using for example.
Pro Extremely easy to integrate Google Services
Because it's made by Google to be the tool to be used for Android Development, it's also very easy for Google to add great support for their services in the IDE and make it easier to integrate Google Services into Android applications built with Studio.
Pro Supports many platforms
Linux, Windows, and Mac are supported.
Pro Allows GPU tracking
For graphics-intensive apps or games, Android Studio has a GPU profiler baked in. With this you can see exactly what is happening inside the device when a new image is drawn on the screen.
Pro Extremely fast preview
Since Android 2.0, Google have been focusing more and more on the IDE's speed, going so far as making it 2-2.5 times faster than older versions.
But the greatest feature when it comes to speed though is the new feature called "Instant Run". This is comparable to writing HTML, where you write the HTML and just refresh te page to see the changes. On mobile though, updating anything would take a lot of time for the system to rebuild.
Instant Run allows developers to build their app once (on physical devices, emulator or both) and as they change their code, AS does hot code swapping where it only updates the parts of the code that have been changed and the developer can see those changes after a second or two.
Pro Pushes fast to the built-in emulator
Pushing to the built-in Android emulator can be up to 10 times faster than pushing to a physical device.
Pro Can test Google Play Services API straight from the emulator
Since the built-in emulator has Google Play Services like a physical device, you can test a lot of API calls without having to deploy your application to a device.
Con Slow runtime
Online IDE is much slower than desktop one.
Con Many errors that are almost impossible to remove
Gradle sync fail
Class can't be found
Update SDK (even with latest version)
Con Many offline issues
Con Apps run slow on the ARM version of the emulator
While the Android team have recently fixed issues that had to do with emulation on an x86 architecture and greatly improving emulator speeds, emulating an Android device and running apps on an ARM architecture is still pretty slow.
Con High memory use
Con Android development only
Android Studio is the official IDE for Android and it works great as an Android IDE. Unfortunately, that's the only thing it can do. If you want to develop applications for other platforms in Java, you have to learn another IDE as well.