Google Previews Android Studio 2.0 (sdtimes.com)

dmleonard618 writes: Google is gearing up to release Android Studio 2.0 with three key features. The company has released the preview version of the release, and says it focuses on speed of delivery and testing. The new features include Instant Run, which lets developers see the impact of their code changes; Android Emulator, a rebuilt user interface; and an early preview of a new GPU Profiler that allows developers to record and replay graphics-intensive apps frame by frame.

Comments

Speedy Delivery

[bigpat]

Approx. 2 month cycle for minor versions. 12 months for major versions. Bug fix versions out in a week or two. That is some aggressive development.

http://tools.android.com/download/studio/stable

Re:Speedy Delivery

[JackieBrown]

Do you want it too? I'd rather not have apps able to touch that.

Still prefer vs 2015

[Billly Gates]

I love the hyper-v emulators more

Re: Instant Run sounds nice

[SQLGuru]

You'd be surprised how hard it is to get some companies to spend money on hardware.......in spite of how much more productive it would make their people. There's still arguments about whether to spend $100 for a second monitor......and that $100 is a one time spend over many years. Memory is in the same boat --- $100 to $150 that will last several years. The payback is almost instantaneous.

These IDE's just get int the way.

[c0d3r]

ADT and Android Studio just seem to get in the way for me. Many times, i've been troubled trying to compile apps with ADT and Android Studio. I used to have to create the project with ADT and Load it into Android studio sometime.

android create project straight from the shell just works better for me. Ant compiles quickly, why compiling with Android Studio just takes forever. Even this new gradle thing doesn't seem to work well. What is gradle supposed to buy me? I just want it to make, not download a bunch of crap first.

Android Developers Blog post link

[bad_fx]

Here is a link to the blog post on this, with much better info that the link in the story:

http://android-developers.blog...

Wiil it work on a 64-bit Linux system now?

[mark-t]

Or does it still require 32-bit compatibility libraries?

How does it compare to Eclipse?

[Snotnose]

I'll be honest, I don't write apps for profit, I just scratch itches. That said, I fire up Eclipse maybe 2-3 times a year. Just about every time it drives me nuts, it's counter-intuitive to my way of thinking. Doesn't really help that I only fire it up when I either need a debugger, or load my app to my phone.

When I say "2-3 times a year" I mean "2-3 groups of using it". I may fire it up 2-3 times a year, but each time I actually run it maybe 10-15 times. So I run it in clusters. Just when I start to get used to the interface I've solved my problem and won't use it again for another several months.

Re:How does it compare to Eclipse?

[Phil Urich]

It's still a very heavy IDE, and I don't know about you but it's the heavy IDE nature of Eclipse tended to be what I experienced friction with personally. That being said, Android Studio (at least prior versions, haven't tried this one yet) is lighter and better organized than Eclipse, if still generally following the same paradigms, and is generally more tuned to specifically developing for Android than their copy of Eclipse was (although it's worth mentioning that Android Studio is also based on an existing IDE, in its case IntelliJ IDEA).

So, I'd say that compared to Eclipse, Android Studio is an improvement, but not a categorical one.

Re:How does it compare to Eclipse?

[interval1066]

For what its worth, I prefer AS. Eclipse is a huge pile of fuck as far as I'm concerned.