Live data from Hacker News

Android M Developer Preview and Tools

android-developers.blogspot.com

31–40 of 153 posts

Re: Android M Developer Preview and Tools

#31
post #13

Earlier quoted context omitted.

I like how people see Android developments as a choice of heavyweight IDEs. I do all my Android development, Java and native, with Emacs and Buck.

Can you recommend any good resources learning about taking this approach?

http://buckbuild.com/

Re: Android M Developer Preview and Tools

#32
post #21

Earlier quoted context omitted.

Dave stated during the keynote that they were slimming down the number of permission categories.

"Dave stated during the keynote that they were slimming down the number of permission categories." So ... they're taking a terrible problem and making it even worse ?

I disagree. I don't know that they've got the right balance until I try it, but anything is better than eg Facebook having permission to just about everything and presumably using it whenever some algorithm tells them there might be useful data to grab.

Forcing them to ask every time will either show my concern is wrong (a good thing) or stop them doing it (even better).

Re: Android M Developer Preview and Tools

#33

> Battery - We’re making Android devices smarter about managing power through a new feature called Doze. With M, Android uses significant motion detection to learn if a device has been left unattended for a while. In this state, Android will exponentially back off background activity, trading off a little bit of app freshness for longer battery life. Will this improve wakelock performance that has been plaguing Andro…

The keynote claimed they took two identical Nexuses side by side with Lollipop and M loaded it up with a bunch of common apps. The standby battery time with M was around double.

Apparently apps could use priority notifications got wake devices up early. Expect Facebook and the rest to go priority priority priority...

Re: Android M Developer Preview and Tools

#34
post #29
post #26

Earlier quoted context omitted.

Do you use Kotlin with Gradle? I like Kotlin a lot, but it feels very slow on my laptop, do you know if there any special optimizations to make it faster?

I haven't shipped anything to production yet but I haven't noticed any build slow downs. I have only really worked through Koans repo to try and learn the paradigms. It can pretty much do anything Ruby, Python, JS, etc can do and it only costs you a 200KB runtime. You might want to make you have parallel builds and the gradle daemon on for the gradle CLI. Android Studio seems to turn these on for you but if you build…

Right, the runtime speed of Kotlin is very good. But the build times got much slower. An average java build with Gradle takes ~30 seconds on my pretty old laptop, but with Kotlin it is about 1 minute. Daemon and parallel are enabled in global gradle properties. I think running Kotlin compiler as a daemon would help, but I don't see an easy way to do that with Gradle.

Re: Android M Developer Preview and Tools

#35
post #27

Earlier quoted context omitted.

Wait, wouldn't slimming down categories result in even less granular control?

I assume that the upfront permissions prompted before an install will be simpler and fewer, and the more granular permissions (like microphone or camera access) will be prompted when they are actually requested by the app. Just like iOS.

Don't think so, as their post install UI slide showed pr category switches with categories very similar to those already seen in the "improved" Play app.

Re: Android M Developer Preview and Tools

#36

Google is showing off Android M dev previews while devices sold new last fall in major US retailers are still running KitKat with no updates from Google or their providers. They continue to actively create the "fractured" world of Android. In other words, that's cool about Android M, but most people aren't even using L. (40% on K, 9% on L whose preview was the 2014 IO) Can Google not poach one or two of Apple's negot…

Only way i see Google getting them all onboard is revenue sharing from Play based on what Android version the person is using.

Re: Android M Developer Preview and Tools

#37
Permissions

"We are giving users control of app permissions in the M release. Apps can trigger requests for permissions at runtime, in the right context, and users can choose whether to grant the permission. Making permission requests right when they’re needed means users can get up and running in your app faster. Also, users have easy access to manage all their app permissions in settings."

Great, finally Google got it. Hopefully with the old Android 2.3 style fine granular permissions and not the few permission groups of Android 4/5.

Re: Android M Developer Preview and Tools

#38
IMO, the most game changing feature announced today is 'Now on tap'

Google isn't releasing more details on it, but with it, Google would be able to understand what you do, when you do it, who your pals are, who you go out to movies with, who you chat with the most, are you looking to quit your job, are you about to break up, are you going through a depression and so on...

They haven't revealed anything about how exactly 'Now on tap' works...but the potential for data collection is enormous. With 'Now on tap' they promise to do 'searches' based on the context (which is derived from the contents in the app that's showing on-screen). So no matter what app you're using, Google will get its hand on the data. It sounds nightmarish and exciting at the same time.

Re: Android M Developer Preview and Tools

#39

IMO, the most game changing feature announced today is 'Now on tap' Google isn't releasing more details on it, but with it, Google would be able to understand what you do, when you do it, who your pals are, who you go out to movies with, who you chat with the most, are you looking to quit your job, are you about to break up, are you going through a depression and so on... They haven't revealed anything about how exac…

What scared me about that announcement was that "no changes in the app are necessary" which basically means that google from now on will parse the text that is displayed, regardless of the type of app that is open.

Without any further clarification i have to expect Google now to send the displayed data of my mobile banking app to its servers everytime i hit that "Now on Tap" button, accidentally or not, while its open. I don't like that.

Re: Android M Developer Preview and Tools

#40
post #16

https://4.bp.blogspot.com/-LCRPmN9Lx_E/VWc6aVDdMkI/AAAAAAAAB... That image... Seriously, when will Google stop doing things like these? Will they ever learn to be attentive?

What are you referring to?

The image is blurry and the colours are dithered. This really looks good to you? https://i.imgur.com/r3HZWyG.png
Post reply on HN