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
Over 2 million developers have joined DZone.
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

  • Lease Coordination Under Serializable Isolation in CockroachDB
  • Java in a Container: Efficient Development and Deployment With Docker
  • The Serverless Illusion: When “Pay for What You Use” Becomes Expensive
  • The Art of Token Frugality in Generative AI Applications
  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 user avatar
Alec Noller
·
May. 22, 23 · Interview
Likes (1)
Comment
Save
Tweet
Share
17.5K Views

Join the DZone community and get the full member experience.

Join For Free

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

The likes didn't load as expected. Please refresh the page and try again.

  • 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