I implemented a small project using Android Studio to get an impression how it works out for me, compared to Eclipse. This post is not meant to start a flame towards IntelliJ, it's meant as a discussion starter.
My Eclipse install is heavily customized, just like my OS. I use a VIM plugin, a ton of auto formatting and a lot of the settings that are by default turned off (some of them, like the auto complete popup delay are beyond any reasoning).
I invested a lot of time to configure Android Studio in the same way (using Google and the settings search bar) but I am still missing a few things. I also deliberately did not change the default keybinds - switching IDE but keeping keybinds seemed like a stupid idea to me.
After working about 40 hours with Android Studio I have to say that it's a nice IDE but I don't really like it. A list of reasons and things that I really miss compared to Eclipse follows below. Note that I'm not (knowingly) talking about things that are still buggy (but being worked on) like multi project support. I am just talking about fundamental Android Studio/IntelliJ flaws. Some of them could be remedied by supplying a better default config, some of them will require further development of Android Studio.
- It does not support save actions like Eclipse does. You can do stuff on VC commit but that would require me to use a gui for git (which I refuse)
- The method signature default popup timeout is 1 second (!)
- Methods are auto completed with foo(); even if they have a signature. Pressing autocomplete (ctrl+space) inside the parentheses will not give any suggestions.
- Completion is case sensitive on the first character by default.
- New file is bound to alt+insert (instead of ctrl+n like everywhere else) and creates a file in a random folder (90% of the time it's the bin folder) it can also not be done while the focus is in the code area. That's not a good thing if you try to avoid the mouse as much as possible.
- There is no way to make it insert semicolons at the end of a line (like in eclipse). This is the second best setting eclipse has to offer (after save actions). Pressing magic complete (ctrl + shift + space) is not an option for me (3 keystrokes instead of 1).
- Most keybindings are considerably longer than their eclipse counterpart.
- It sometimes refuses to show javadocs when using the keybind and gives no reason why it does so.
- Logcat has no columns and does not support filtering by application via double click. Also, the window gets cleared immediately when disconnecting a device. This is absolutely NOT acceptable and does not provide any benefit to a developer.
- package / app renaming is a HORRIBLE, HORRIBLE experience. After figuring out what the difference between folder and module renaming is, you still have to update a trillion things by hand (like gradle files). Also, when restarting Studio
- Package moving and renaming is absolutely counter intuitive. I have not found a way to rename foo.bar.baz to wtf.omg without using 2 gui windows (one for rename, one for move). Eclipse rename is not that intuitive either but at least it works.
- Mouse over tooltips (in the IDE, not the editor) take way too long to show.
- IntelliSense is supposed to be nice but it does not really help a lot when you have to manually start it with ctrl+shift+space all the time (Eclipse autocomplete with a-zAZ09.( as hot chars and 0 ms delay is way better).
- It requires OracleJDK or will not start up without a warning. When started with OpenJDK, fonts are rendering like crap.
- When used with awesome WM it requires a random combination of change screen, fullscreen and change screen layout so that the right mouse menus and so on are on the correct screen. So far I had NO application that had those problems (see screenshot below). It also does not label the sub windows (seems not to register them with the Window manager).
- Deleting modules from a project is sometimes not possible. Removing via shell requires to restart intellij so it figures out what is going on (seriously, "remove module" is greyed out), and they sometimes remain as empty arrows. (see screenshot below)
- It comes with it's own Android SDK folder and cannot be changed globally.
|Empty entry in the Project structure|
Overall I don't see the benefit of using Android Studio over Eclipse. Granted, it's a bit faster than Eclipse (but using Linux drives down my compile times to a level where I barely notice them), XML editing works a lot better and seeing the drawables on the side of the editor is a nice idea. Seeing the actual strings instead of R.string.foo is... okish, but it confuses me a lot more than it helps - I guess that's something to get used to. Gradle has a lot of potential and is an extreme improvement over ANT, but it misses things like git dependencies (bundler ftw).