Live data from Hacker News

Android Studio 3.2

android-developers.googleblog.com

11–20 of 84 posts

Re: Android Studio 3.2

#11
post #10
post #8

Earlier quoted context omitted.

Developing for the browser is leaner but it's the opposite for end-users. I hope PWAs are the future as well but native is still king for the time being.

As a user, I totally prefer a web app over a native app. Man .. don't even get me started .. ok, here we go: I can use it instantly. I can remove it instantly. The sandboxing is much better. The privacy is much better. I can link to it from wherever I like. I can use it on all my devices. I can copy text and images. I can change the style (I often enlarge the font for example). It can not use my battery / camera / ph…

I open 2 web apps at the same time, and the phone crashes (all RAM exhausted). I open a web app, and it lags horribly for minutes before becoming even semi-usable.

This is on a Nexus 5X, using stock Android.

Web apps are a complete joke right now. Entirely useless. I always install native apps, if available — even if I know I’ll uninstall it 5 minutes later — because the alternative is entirely unusable on my device.

Re: Android Studio 3.2

#12
post #11
post #10

Earlier quoted context omitted.

As a user, I totally prefer a web app over a native app. Man .. don't even get me started .. ok, here we go: I can use it instantly. I can remove it instantly. The sandboxing is much better. The privacy is much better. I can link to it from wherever I like. I can use it on all my devices. I can copy text and images. I can change the style (I often enlarge the font for example). It can not use my battery / camera / ph…

I open 2 web apps at the same time, and the phone crashes (all RAM exhausted). I open a web app, and it lags horribly for minutes before becoming even semi-usable. This is on a Nexus 5X, using stock Android. Web apps are a complete joke right now. Entirely useless. I always install native apps, if available — even if I know I’ll uninstall it 5 minutes later — because the alternative is entirely unusable on my device.

That does not make sense. Web apps do not consume more resources then websites. And usually less then native apps. I never had them crash any phone.

Re: Android Studio 3.2

#13
post #6

I try Android Studio for a bit every now and then. I have to say it's such a giant bloated thing that it really does not make me want to write native code. Fortunately, there is a lot of great stuff going on with Progressive Web Apps now. I hope that they will be the future. Developing for the browser is so much leaner.

Yay for PWA! Please, if you're developing PWA's be sure to share them on all the marketplaces! Hardware/OS freedom would be amazing!

Re: Android Studio 3.2

#15
Most exciting feature: App Bundles! At last, users with an Galaxy S5 won't have to install the same APK as a Note S9. This will especially helpful to users in countries where data is expensive, phones are old, and storage is low. Also, I can see this ensuring users download through the app store, since app pirates (most of the time, injecting trojans into free programs), will have to upload many different APKs in order to "trick" users into installing their APK.

The Energy Profiler is a nice addition, but I wish there was some incentive for apps to be energy efficient (even an app store "badge" would be better than nothing), since people will continue to just blame Android for the battery performance and not the apps.

super-small-nit: It's Android Studio 3.2, but the installer's file name is android-studio-ide-181.5014246-mac.dmg. android-studio-3.2.dmg would of been just fine. I am guessing 181 is a build number, but as a user, I don't care about what build number it is.

Re: Android Studio 3.2

#18
post #10
post #8

Earlier quoted context omitted.

Developing for the browser is leaner but it's the opposite for end-users. I hope PWAs are the future as well but native is still king for the time being.

As a user, I totally prefer a web app over a native app. Man .. don't even get me started .. ok, here we go: I can use it instantly. I can remove it instantly. The sandboxing is much better. The privacy is much better. I can link to it from wherever I like. I can use it on all my devices. I can copy text and images. I can change the style (I often enlarge the font for example). It can not use my battery / camera / ph…

Do you use a web app or a native app for YouTube?

Re: Android Studio 3.2

#19
post #12
post #11

Earlier quoted context omitted.

I open 2 web apps at the same time, and the phone crashes (all RAM exhausted). I open a web app, and it lags horribly for minutes before becoming even semi-usable. This is on a Nexus 5X, using stock Android. Web apps are a complete joke right now. Entirely useless. I always install native apps, if available — even if I know I’ll uninstall it 5 minutes later — because the alternative is entirely unusable on my device.

That does not make sense. Web apps do not consume more resources then websites. And usually less then native apps. I never had them crash any phone.

A web application burning through a ton of JavaScript and a very complex DOM can very easily start demanding a lot of CPU and RAM.

I've never had a browser crash a phone, but having the phone start to immediately feel sluggish after opening something like a moderately sized GitHub pull request--that's certainly a thing.

Re: Android Studio 3.2

#20
post #6

I try Android Studio for a bit every now and then. I have to say it's such a giant bloated thing that it really does not make me want to write native code. Fortunately, there is a lot of great stuff going on with Progressive Web Apps now. I hope that they will be the future. Developing for the browser is so much leaner.

Yay for PWA! Please, if you're developing PWA's be sure to share them on all the marketplaces! Hardware/OS freedom would be amazing!

Isn't windows mobile the only platform where PWA's can be submitted to the app store?
Post reply on HN