Pete Letkeman wrote:When preparing for the Java certification tests it is recommended that one does not use an IDE.
It appears as though some people are 'married' to their IDE and all of the extra features which are supplied either naively or via plugins.
In your book Head First Android Development (2nd Edition) do you recommend any particular IDE and if so why?
Pete Letkeman wrote:... which are supplied either naively or via plugins.
Tim Holloway wrote:"Naivley" is precisely why we discourage the use of IDEs for general Java development. Yes, I'm sure you meant "natively"
Tim Holloway wrote:However, I'll admit that I've never developed for Android outside of an IDE. I got into too many fights with its magic resource generator requirements and I've never bothered to get properly educated on the Maven plugin (most of my projects are Maven-built).
Pete Letkeman wrote:I think that initially when Google provided the Android Development Tools for Eclipse that Maven was recommended. However with the release of Android Studio doesn't Google/Android recommend Gradle? Is there any reason as to why you choose to use Maven over Gradle Tim?
Tim Moores wrote:Maven was never much used for Android. Initially, Ant was the preferred built tool,
In using the ADT for Eclipse don't you run into the possibility unknown errors.
paul nisset wrote:Don't go the notepad route for Android. You really do need an IDE to learn it initially. An IDE also has things like Emulators that speed up development.