Android M Developer Preview and Tools • Hacker News Board

Re: Android M Developer Preview and Tools

#21

Post by rsync » Thu, May 28, 2015, 7:38 PM UTC

EddieRingle wrote: post #4

JasonFruit wrote: post #2

The update to provide run-time permission prompts pleases me as a user; as a developer, I'm not as excited about it, especially if it doesn't come with narrower categories of permission. I could see it prompting the user to provide permission to do much more than is being done, and without the ability to provide reasoning and context in the dialog.

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 ?

Re: Android M Developer Preview and Tools

#22

Post by zserge » Thu, May 28, 2015, 7:39 PM UTC

quotemstr wrote: post #8

amolgupta wrote: post #3

the NDK support in Studio will end the use of eclipse for Android development.

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.

Oh, finally I'm not alone here! I use vim/tmux and yesterday I discovered Buck and made a quick project generator: http://zserge.com/blog/buck-build-system.html

Re: Android M Developer Preview and Tools

#23

Post by nly » Thu, May 28, 2015, 7:46 PM UTC

runjake wrote: post #14

jfuhrman wrote: post #12

Will there be an official Android M for the Nexus 4 ? It's a very powerful device even by today's standards with a quadcore and 2GB RAM.

From the article this submission is linked to: "The M Developer Preview includes an updated SDK with tools, system images for testing on the official Android emulator, and system images for testing on Nexus 5, Nexus 6, Nexus 9, and Nexus Player devices." So, no.

I don't think they released the Android L previews for the the N4 either? Maybe someone can confirm.

Re: Android M Developer Preview and Tools

#24

Post by amolgupta » Thu, May 28, 2015, 7:47 PM UTC

mahouse wrote: 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?

Are you talking about the overlapping chat bubbles? Yes it us ugly and easy to miss.

Re: Android M Developer Preview and Tools

#25

Post by jaredmcateer » Thu, May 28, 2015, 7:54 PM UTC

heyheyhey wrote: post #11

> 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.

Re: Android M Developer Preview and Tools

#26

Post by zserge » Thu, May 28, 2015, 7:56 PM UTC

jophde wrote: post #19

quotemstr wrote: post #8

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.

The thought of writing Java without IntelliJ makes me want to quick programming. Ironically, Kotlin might be great in a text editor despite being made by Jetbrains.

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?

Re: Android M Developer Preview and Tools

#27

Post by baddox » Thu, May 28, 2015, 8:09 PM UTC

lsaferite wrote: post #9

EddieRingle wrote: post #4

Earlier quoted context omitted.

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

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.

Re: Android M Developer Preview and Tools

#28

Post by 27182818284 » Thu, May 28, 2015, 8:15 PM UTC

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 negotiators to go to the right meetings at Motorola, Verizon, etc to talk about updates?

Re: Android M Developer Preview and Tools

#29

Post by jophde » Thu, May 28, 2015, 8:16 PM UTC

zserge wrote: post #26

jophde wrote: post #19

Earlier quoted context omitted.

The thought of writing Java without IntelliJ makes me want to quick programming. Ironically, Kotlin might be great in a text editor despite being made by Jetbrains.

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 from the terminal I think they need to be specified in a gradle.properties file in the project root. You can also increase the amount of memory gradle is allowed to use.

As far as I know Kotlin does almost all of its magic at compile time so I am sure it will slow down builds slightly versus plain Java. From what I have seen so far I am more than willing to pay this price.

Here is a good overview with benchmarks from Square

https://docs.google.com/document/d/1ReS3ep-hjxWA8kZi0YqDbEhC...

Re: Android M Developer Preview and Tools

#30

Post by sumitviii » Thu, May 28, 2015, 8:25 PM UTC

jaredmcateer wrote: post #25

heyheyhey wrote: post #11

> 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.

*Up to double.