Google I/O 2015 - Android M Permissions

[@e_ri9451]

It's about damn time, Google. You have kept me away from Android because of the problem of app permissions and how you either have to accept all permissions or none if you want an app. Now we can have full control over permissions. Maybe now I'll switch back to Android..

[@VIDEOSGZED]

thank you and very informative. one question I've always wondered is this: when an app has permission to read the information about an incoming caller, how is it at all possible for that individual to give that permission when they are calling a party who they may have no idea about which apps that party has installed? any insight/answer world be greatly appreciated. cheers!

[@PremSuraj]

This is one talk you can't afford to miss if you are a developer..

[@killer25318]

I just wanna say as a user I have been waiting for this for a long time

[@ramdenze]

Lets turn it around once more. Change the platform every day if you can please, maybe every hour? I love to write code that is 20x bigger than on 5.X. Maybe with android 7 I have to write 20k lines for 3 screens, no problem at all

[@ybra]

18:07 that seems like a very valid question. Why should apps have automatic internet permissions? Even if the app can't get data from your phone, isn't blocking internet permission also a good idea?

[@rajat.sharma16]

because that would have prevented google from automatically scrapping your data. It's an ad company after all. :)

[@2ma]

There are still permissions grouped that don't belong together. If I need access to the phone state, because I need to handle something differently when the device is in a call, I need access to the phone permission, but the phone permission shouldn't be given to anything unless it specifically handles calls. Also giving access to any app to the internet has still a lot of security problems, even if the app can't access user data.

[@RomanOnARiver]

Are the dialogs like "don't ask again" system defined or is it up the app? Can they be themed by the app to look better (in the positive) or by malicious apps to be deceptive (on the negative)? In short, is there something blocking malicious apps from running a do-until until the permission is granted or for that matter being generally annoying - playing loud noises until it gets its way, etc?

[@m.m_travel]

I am a Samsung and android fanboy..but I have to admit, nothing beats apple's keynotes.

[@osullivanja]

16:59 If I'm understanding this right, this means that an app that communicates with a Bluetooth device, such as every Android Wear app, is going to have a pop up that says it needs access to your location?

[@FeelsDonkMan]

The libraries question worries me, but overall I suppose this is a good move forward for Android.

[@DennisBareis]

The new App permissions seem to have been well though out and better than I expected. Unfortunately developers are currently not able to supply (directly in the permissions request) a reason for the app asking for it.

[@juraad]

Dennis Bareis As I understand it, it should be clear to the user from the context. I click a "Center the map onto my location" and the app prompts me for location permission. I click "Take a picture" and I get prompted for camera permission. Alternatively, the app shows me a quick start screen that walks me through granting the permissions that will be needed one at a time. It is a lot more work this way, but when the interaction flow is done right, it feels much better.

[@MadisOtenurm]

Dennis Bareis They have to put the reason before asking into the app itself. See 16:28

[@DennisBareis]

Madis Otenurm They don't NEED to, it would be wise of they did.

[@MadisOtenurm]

Dennis Bareis Well, yeah, but the point is that app should say the reason, not the OS.

[@DennisBareis]

*****​ Asking in the right content is obviously best, but somethings will not always be obvious, but then again this is only for high level permission groups at the moment so maybe not so much of an issue...

[@remmievail8148]

Is there a reason permission request results invoke onRequestPermissionsResult on an Activity/Fragment instead of allowing us to provide a callback?

[@刘毅-d7j]

From developer.android.com says: "For the preview release, you must set the minimum SDK version to the M Preview SDK to compile with the preview SDK. This means you will not be able to test such apps on older platforms during the developer preview." Now question comes: How to install M preview app to the older platforms devices?

[@parthdave8555]

What happens if I have background service which takes GPS location. now I'm seeing that when user turn off the permission the service restarted and at that time I sent a local push notification but user turned on permission from settings at that time it won't start again.

[@DanieleSegato]

Do the API let me know if the user checked the "don't ask again"? If yes, does it only tell me immediately when I get the result or I can query for it anytime?

[@MichaelPrentice]

Yes. Not sure.

[@RameshAkula]

+Michael Prentice what is api for that ? I didn't find anything in docs..

[@ybra]

Anyone know when this will be live?

[@jvsantillo]

Great talk, it helped me a lot!

[@nadruf]

you need android M 2015 WHY? i have oold phone with app permission from custom rom

[@jeremyweasley8079]

These feature should learn from iOS earlier to avoid permission abuse from malware in the third party software. Why I switched my phone to iPhone is because the permission controll sucks compare to the iOS

[@edmundo2dot0]

I hate this, introduces a ton of unneeded confusion, I feel this will be the version of Android where everything goes down the hill, especially with apps that haven't been updated in a while

[@MichalCanecky]

Here is how it will work in reality: Let's say I want to install Angry Turds. AT will ask for permission to access my GPS, contact list, phone, SMS, photos, camera, microphone and my anus. Since I don't think it needs to access any of those to play the game I will give no access to any of those. The game will display "Sorry but we need those permissions to better serve you" and exits. We as users will be exactly in the same position as we are now, when we are being blackmailed by apps to give unreasonable permissions to run them.

[@MichaelPrentice]

This is certainly a real possibility that sketchy apps will try to leverage. Hopefully it gets them a lot of 1 star reviews.

[@RomanOnARiver]

Michal Canecky I'm concerned about this as well, and this will mean the shitty app cannot run, but at the end of the day, the shitty app also won't have your data, so that's a plus.

[@ramdenze]

+Roman V How would you recognise a "shitty app" if the app does not ever function because you said deny?

[@WestDerwin]

1+ from me.

[@CapsAdmin]

I've already experienced this as a user. It would be much better if developers didn't know what choice the user went with. If the app needs to access the contact list and the user says no it should instead give a dummy contact list to read from and write to.

[@clarencetabsares5762]

why my game is billing

[@davideschembari3026]

This presentation was meant to explain the nitty gritty. The two main API's, checkSelfPermission(...) and requestPermissions(...), where from?! Could you have bothered to put which classes they belong?! Very shoddy.

[@MichaelPrentice]

I think he expects you to RTFM for this critical feature. But I agree that more code would have been good.

[@davideschembari3026]

Michael Prentice Yes, fortunately there's a nice code sample which explains everything. But if you go all the way to I/O and pay for it, you'd expect something better. They can improve their presentations at I/O in my opinion.

[@MichaelPrentice]

Yes, the streamed videos for this year's I/O were extremely light on actual code. Good news is lots of code labs and references exist and Dev Bytes are coming out daily to help address this.

[@xaionik]

Dumb developers are going to blast everything upfront.

[@camelCased]

Yeah, and now you have to turn on expensive battery-draining GPS when you want to look for BLE devices. Ugly. This has bitten many BLE developers.

[@chuckbarnett_tx]

marshmallow permissions are a joke

[@spaminbox]

what about device and app history, where did it go, and as a user, how do i deny it?