Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
I'm starting to develop for Android. Which IDE should I use - Android Studio or Eclipse sdk?
I would like to know which one is better.
Working with Eclipse can be difficult at times, probably when debugging and designing layouts Eclipse sometimes get stuck and we have to restart Eclipse from time to time. Also you get problems with emulators.
Android studio was released very recently and this IDE is not yet heavily used by developers. Therefore, it may contain certain bugs.
This describes the difference between android android studio and eclipse project structure: Android Studio Project Structure (v.s. Eclipse Project Structure)
This teaches you how to use the android studio: http://www.infinum.co/the-capsized-eight/articles/android-studio-vs-eclipse-1-0
The use of IDE is your personal preference.
But personally if I had to choose, Eclipse is a widely known, trusted and certainly offers more features then Android Studio.
Android Studio is a little new right now. May be it's upcoming versions keep up to Eclipse level soon.
Both are equally good. With Android Studio you have ADT tools integrated, and with eclipse you need to integrate them manually. With Android Studio, it feels like a tool designed from the outset with Android development in mind.
Go ahead, they have same features.
From the Android Studio download page:
Caution: Android Studio is currently available as an early access preview. Several features are either incomplete or not yet implemented and you may encounter bugs. If you are not comfortable using an unfinished product, you may want to instead download (or continue to use) the ADT Bundle (Eclipse with the ADT Plugin).
My first choice is Android Studio. its has great feature to develop android application.
Eclipse is not that hard to learn also.If you're going to be learning Android development from the start, I can recommend Hello, Android, which I just finished. It shows you exactly how to use all the features of Eclipse that are useful for developing Android apps. There's also a brief section on getting set up to develop from the command line and from other IDEs.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
My company gave me a 4 year old Android Project that I have to fix. I've been used to working with IntelliJ and Android Studio for a while now. At first sight I saw this was an eclipse project and I've tried numerous things to get this to work on Android Studio, more specifically like the following.
I'm also trying to integrate Gradle in this project. But even after trial and error I do not get the expected result that I normally get with my own projects, note the arrows I usually get with my other projects. Now it looks totally different.
Any help or tips on how to get this old project back on its feet is highly appreciated.
This could help you a lot:
Migrating from Eclipse ADT
Another critical thing is that if you are a keyboard-oriented programmer, it will take some time to get used to Android Studio's shortcuts. Even though it has some eclipse shortcut support.
Which can be easily found in here:
Eclipse Shortcuts
Good luck.
You can follow the following steps, no need to export the projcet as Gradle, Android Studio (AS) provides this by default,
Go to File menu and select New -> Import Project
next from the File browser select your Eclipse Project folder,
click Next in the subsequent steps and lastly Finish to successfully import the project
There may be some dependncies of your project but you can read the instructions provided by the Android Studio import dialogs and handle them,
ask further if you need help.
In the worst case scenario, you can always make a project by the same name, copy the sources (and resources) into their corresponding package, move the relevant stuff from the old AndroidManifest to the new, and add the external dependencies (such as that Google Play Lib for example) through Gradle itself.
If the project uses NDK, then you're gonna have a bad time though, because that requires setting up the Gradle experimental branch.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
What are the main differences between using Eclipse with the Android plugin and the standard Android Studio?
Which one do you recommend? (I guess it varies with how we plan to use it).
Thank you in advance for the help
Please use Android Studio, Eclipse is no longer supported. You can import your Eclipse projects and use them in android studio. Also check the following questions:
Android Studio vs Eclipse with ADT (2015)
Which Android IDE is better - Android Studio or Eclipse?
Finally, I found the following two reasons to be great positives to use Android Studio:
It supports gradle (this allows you to really have control over the build, create different application flavors, different signing configurations and so on).
It feels better. From doing a refactoring (like renaming a method, to extracting a class) to viewing the Logcat. The refactoring seem more solid and the Logcat does not "disappear" as it happens in Eclipse.
Eclipse is basically for Java program development and used for Android with ADT, whereas Android Studio is available specifically for Android development and you will get a lot of help with it.
Studio is definitely better for designing layouts running emulators.
Studio provides better debugging and help popups when you start coding.
I would recommend you go ahead with Android Studio as it will prove to be helpful even if you stuck somewhere with the method names or anything else.
Eclipse sucks. Go for Android Studio which is based on the unbeatable Java IDE - IntelliJ Idea (known as JetBrains Idea these days).
Android Studio uses the dependency and gradle structure whereas eclipse do not use it.
I recommend you to use Android Studio. It is the Best for Android Programming. Some newer updates are not available in Eclipse. Android Studio does has.
These are few positives :
No R file errors, it gets generated at compile time and uses stub for development.
Very good and fast autocomplete feature
Preview of resources (Drawables, styles, etc) along side code
List of layouts used in a class file
Analyse code and fixes it using single click (LINT tool is used for this). This tool is very good, you also learn about your mistakes too
References of methods (shows parts of code from where a method is called)
Builtin support for ANT, Maven, gradle, git, svn, etc, etc
No need for extra plugins for Android
Better visual editor than Eclipse
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
Recently developed a project on eclipse and was published. Yesterday I tried to create another project and it was not possible. I went up to the developers website to download the latest version, and found not download the ADT. I found just downloaded the Android Studio. Does anyone have any info on this?
Obs .: Question made with Google Translator help. Excuse me anything.
Yes, though Google may be extending support for Eclipse for a while longer, considering that:
Right after Android Studio 1.0 is released, Developer tools page has the following wording:
Caution: The ADT plugin for Eclipse is no longer in active
development. If you're currently using it, you should migrate to
Android Studio as soon as possible. For more details about Android
Studio, see the Android Studio guide.
And now the wording has been changed to:
Note: If you have been using Eclipse with ADT, be aware that Android
Studio is now the official IDE for Android, so you should migrate to
Android Studio to receive all the latest IDE updates. For help moving
projects, see Migrating to Android Studio.
Where they removed the statement "The ADT plugin for Eclipse is no longer in active development".
Regardless, developing Android using Eclipse is something that will become impossible some time down the road, so it's better to download Android Studio now and start migrating your Eclipse projects with the help of migration guide.
Yes, Android Studio is now out of beta and is the official IDE. The Eclipse plugin will no longer updated.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I used to be an Android developer for 2 years, but over 2 years ago. I believe that things changed - we have Android Studio, Gradle and probably more tools that I'm not aware of right now.
What is the current development stack for creating Android applications? What tools should we used right now?
I used to use eclipse with ant, but as far as I can see, a lot of people are using AS with Gradle, which is, for my first experience, extremely slow.
How to jump back into Android development after some time of not being up to date with development stack?
Eclipse vs Android Studio is a matter of choice. You can get used to it within hours, or you can continue with Eclipse. I am using both tools for different projects.
Android Studio seemed to be more stabile at some points.
Update on Android SDK and third party libraries are more easily handled with Android Studio.
Android Studio has not NDK support yet. You have to compile native codes outside of Android Studio. Edit:(Well, actually it has support but claimed to be deprecated, probably developers are working on a better solution)
Edit2:(It will be soon officially supported with C/C++ debugger)
With Android Studio you can use java7 syntax, but you have to stick with java6 syntax on Eclipse. Edit:(you can now force java8 with a plugin on A.S and I guess java7 is usable on eclipse too) Edit2:(java7 is a must now for both parties, but still java8 syntax can only be used in A.S with a help of plugin)
Google releases example codes compatible with Android Studio saying eclipse versions will be available soon.
Android Studio has better GUI designer.
Android Studio has better refactoring capabilities.
The most important change is SDK itself, actually. Just check if Android Studio is good enough for you and study on SDK.
It depends on your project. For non critical or hobby projects you should definitely start with AS and Gradle right away because this the the future of Android development. Although it is still in 'beta' and it can break some stuff after a new upgrade, it has many new features which make you more productive and happier in development.
If you have a critical project and you don't want to spend your time with checking and fixing things your are not supposed to fix, you should stick back to Eclipse, at least until AS is released.
Independently on whether you use AS or Eclipse, you should already start learning and using Gradle. It works perfectly for both options. If you hesitate you can even keep Ant and Gradle building your project in parallel. They work together and don't overlap.
I have been using Android Studio the last year and I can say that it is a very powerful tool, that I believe, in the next year, will overcome Eclipse.
When AS was still in version 4.+ Alpha, there were some issues (mostly with external libraries .jar) but since beta was released and up until now almost every bug was fixed.
Moreover, AS is better when it comes to indexing and suggestions. You will be surprised by its suggestion system, which helps you save a lot of time when coding.
I still use eclipse for other projects, but I believe for Android Development AS is the tool you should invest in, if not for now, definitely for the future.
We are using both, Android Studio and the good old Eclipse IDE. We noticed, that it basically depends on what you're doing. Android Studio is good enough for developing from now and it will replace Eclipse soon. However, it has some drawbacks where Eclipse is your choice. A small comparison was made by Google themselves: https://developer.android.com/sdk/installing/studio.html
Eclipse: Eclipse is very stable and works perfectly with ant driven builds. However, if you want to use gradle, there's some work to do to get the build process working with eclipse. We tried to use Eclipse with Gradle but the Gradle Plugin was quite buggy at this time. If you want to use native C code, you must use Eclipse, as Android Studio does not support that, yet.
Android Studio: Looks great and does also a very good job. The gradle integration works much better there. This is a big advantage over Eclipse when you have to deal with many dependencies. This is probably not an issue for small projects. But, if you're developing projects with additional libraries or frameworks you should definitely give Gradle a try. I hope, that the NDK support is coming soon, so that we can switch to AS completely. Ant builds are someway out-dated.
First of all, I will not debate about Android Studio vs Eclipse as it's an opinion based discussion and a kind of a troll...
The Android development basically the same : the base tools still ADB, Android SDK, Java language... So you can continue to use a "notepad" and compile, build and deploy by the SDK tools.
However, like in every development project, you could choose your upper level tools. Your question is about IDE and building system. This is only a matter of choice.
Android Studio and Gradle are still in beta phase for Android developments and you could use them only if you keep this in mind. You could continue to use Eclipse and Maven or switch to Android Studio and Gradle or keep using Eclipse but moving from Maven to Gradle... just make what you prefer.
The Android development stack evolved this way :
Basics tools : Text editor, SDK tools
First IDE : Eclipse with ADT plugin (can run your program from an IDE)
Industrialisation phase : Eclipse ADT + Maven (dependencies management, building process management...)
Coming phase : Android Studio (IntelliJ based) + Gradle (you can compare Gradle to Maven, but this is another discussion)
I think that other answers will give you personnal points of view about Eclipse vs Android Studio, Maven vs Gradle, etc... which is a really personnal choice ;)
My development stack for Android :
IntelliJ 14
Maven
Android SDK
plus my own OSS Framework to ease the pain of Android for a Java EE developer
Reasons:
IntelliJ is the best available IDE imo
Maven is pretty mature
The plugin has become useable
The workspace integration Maven -> IntelliJ is working great (both, using maven builds and deriving IDE builds from maven)
If Android Studio (which is in great parts IntelliJ) has become slow, it come due to the gradle stuff. I had a large scale project based on gradle and made these experiences :
Slow, Slower, gradle (up to 2GB memor consumption for building an app)
Xml is horrible, but gradle dsl is imo even worse
Switching to gradle 2.1 broke the predicate logic (e.g. formerly working project.hasProperty("foo") && property.ext.foo.equals("bar") does not work any more, this must not happen during a MINOR release
Compared with maven's xml hell, gradle leaves a callow, unmature impression on me, especially building with gradle is hell of a slow job compared with maven.
But - and this is my true oppionion - if gradle is pushed by google and gradleware, it definitely has the potential to become the next generation building tool, although I doubt that the flexibility in gradle will ever lead to a proper IDE workspace build derivation. From my point of view, the choice for gradle over maven done by google happened in a too early state.
just my two cents.
PS: Try tuning the memory settings. Give more memory to IDEA (e.g. 2GB in a 64bit enviroment). My experience with IntelliJ is, that the default mem settings are too small. You can find it in $InstallDir/bin/idea.exe.vmoptions resp. $InstallDir/bin/idea64.exe.vmoptions
EDIT: This is not intended to be gradle bashing. Gradle has large potentials indeed. This post reflects my experiences during my last project basing on gradle (non-Android). For beginners gradle might be the better choice since it is a lot easier than maven.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 1 year ago.
Improve this question
Since I've got issues with ndk development on eclipse (multiple errors when I open a .c file in the JNI so I cannot set any breakpoint without close and reopen the project after it) I was wondering if any of you has the knowledge of another IDE which would be more effective for an environment where I intent to use the NDK for calling a native library and the SDK for the rest (App gui, calls to lib, etc...)
Many thanks for your advices.
You can use Eclipse, NDK can be integrated there, there are some plug-ins that you can use to debug native code.
I'll recommend to use Android-Studio based on IntelliJ IDEA from jetBrains when there will be a v1 release, its UI is clear and effective and the debugger is less annoying than eclipse's one, however native development is a bit tricky unlike eclipse which provides the appropriated plugins when you write your module in C++ (if you do it in C, the compiler will take it as an error when you'll open your file in the IDE).
So I'll develop in native using eclipse until a native module exists for Android Studio.
How about keep using Eclipse on Linux with full features. Features for Java support and Native language support.
Did you try out Visual studio 2017+ ?
Remember, with Visual studio and C/C++, you can support windows, android, (may be IOs as well but not tried) from single code.
VS is light weight but powerful IDE.
I recommend VS2017.
at visualstudio.microsoft.com:
Write once target all
C++ is a great language for mobile app development
Migrate existing C++ libraries to target Android, iOS, and Windows platforms or use these C++ libraries to build complete Xamarin Android Native, Java Native Interface, >or iOS applications. You can also develop complete Android Native-Activity applications all within Visual Studio.
Article: Build an app for Android, iOS, and Windows (C++)
Article: Mobile Development with C++ | Windows UWP, Android and iOS
Video: Getting started with ndk and visual studio