Android M Developer Preview and Tools

#1

Post by CodeWithCoffee » Thu, May 28, 2015, 6:02 PM UTC

Android M Developer Preview and Tools
android-developers.blogspot.com

Re: Android M Developer Preview and Tools

#2

Post by JasonFruit » Thu, May 28, 2015, 6:15 PM UTC

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.

Re: Android M Developer Preview and Tools

#3

Post by amolgupta » Thu, May 28, 2015, 6:26 PM UTC

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

Re: Android M Developer Preview and Tools

#4

Post by EddieRingle » Thu, May 28, 2015, 6:34 PM UTC

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.

Re: Android M Developer Preview and Tools

#5

Post by tdkl » Thu, May 28, 2015, 6:36 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.

For devices running M. Versions prior to that will be left as is.

Re: Android M Developer Preview and Tools

#6

Post by EddieRingle » Thu, May 28, 2015, 6:43 PM UTC

tdkl wrote: post #5

EddieRingle wrote: post #4

Earlier quoted context omitted.

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

For devices running M. Versions prior to that will be left as is.

Not devices, but applications targeting M, yes.

Re: Android M Developer Preview and Tools

#7

Post by tdkl » Thu, May 28, 2015, 6:49 PM UTC

EddieRingle wrote: post #6

tdkl wrote: post #5

Earlier quoted context omitted.

For devices running M. Versions prior to that will be left as is.

Not devices, but applications targeting M, yes.

The new permission system will be available on devices running M only. So a dev will have to support both when targeting M.

Re: Android M Developer Preview and Tools

#8

Post by quotemstr » Thu, May 28, 2015, 6:55 PM UTC

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.

Re: Android M Developer Preview and Tools

#9

Post by lsaferite » Thu, May 28, 2015, 6:56 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.

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

Re: Android M Developer Preview and Tools

#10

Post by EddieRingle » Thu, May 28, 2015, 6:57 PM UTC

tdkl wrote: post #7

EddieRingle wrote: post #6

Earlier quoted context omitted.

Not devices, but applications targeting M, yes.

The new permission system will be available on devices running M only. So a dev will have to support both when targeting M.

Well that goes without saying. I'm just trying to say that applications running on M and later that still target an older SDK will not use the new system.