4 ms·
Honestly, if you have problems getting used to an IDE, you'll have a huge problem developing for Android anyway - it's a platform that's significantly different
by izacus 12y ago
Honestly, if you have problems getting used to an IDE, you'll have a huge problem developing for Android anyway - it's a platform that's significantly different than any out there and learning the IDE is such a minor thing that developer hung up on that probably shouldn't be developing Android apps.
Also, you're not "forced" into anything - any Gradle compatible Java IDE will load and compile AS projects without a hitch (sadly, Eclipse Gradle support is really bad, hence the switch od IntelliJ platform).
- pjmlp 12y agoEclipse support of any build tool is quite bad, since they are always seen as external tools (looking at you M2E). I rather like the approach taken by Netbeans where they refactored the IDE to use build tools as the project format, with known targets mapped to IDE actions. Same approach taken by Visual Studio as well. Cannot say much about Android Studio, because lack of C++ editing/linting/refactoring/debugging and NDK support keeps me on Eclipse.