DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Elevate Customer Engagement by Adding Google Play Instant to Your Android App
  • Getting Started With Android UI Development With Jetpack Compose
  • Overview of Android Networking Tools: Receiving, Sending, Inspecting, and Mock Servers
  • How to Rectify R Package Error in Android Studio

Trending

  • How to Migrate From LangChainGo to Genkit Go
  • Build a Voice Assistant With Gemini Live API
  • Solving Comprehension Debt in AI-Generated Codebases
  • Testing Java and Spring Applications With Kotlin: Low-Risk to Adoption

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Deployment
  4. How it Feels to Switch from Eclipse to Android Studio

How it Feels to Switch from Eclipse to Android Studio

By 
Alec Noller
·
May. 22, 23 · Interview
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
17.9K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

So, Android Studio exists. While there are a number of fixes for the less-than-graceful aspects of Android development in Eclipse - Genymotion, right? - some are moving to Android Studio for a more stream-lined approach. This recent post from MeetMe's engineering blog details Bill Donahue's switch from Eclipse to Android Studio, and he has some pretty strong feelings about it. He says - and this is his own emphasis - the following:

I will never go back to Eclipse

Donahue then explains the key differences as he sees them. First he makes a list of complaints about Eclipse - constant refreshing, awkward UI building, hogging RAM, and so on - followed by a list of the improvements found in Android Studio, such as full-program themes, new UI tools, better stability and performance, and more.

He does point to a couple of hiccups, such as the switch to a Gradle build, but it's more of a thing you're going to have to learn than an issue with Android Studio. Check out Donahue's full post for more details on the switch and the little things Android Studio does to make it more comfortable.


Android Studio Android (robot) Eclipse IT

Opinions expressed by DZone contributors are their own.

Related

  • Elevate Customer Engagement by Adding Google Play Instant to Your Android App
  • Getting Started With Android UI Development With Jetpack Compose
  • Overview of Android Networking Tools: Receiving, Sending, Inspecting, and Mock Servers
  • How to Rectify R Package Error in Android Studio

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook