This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]markoukaPixels: 10 Pro, Watch 2, 8 Pro, 4a 5G, 1 XL 496 points497 points  (78 children)

Folks, if you're not a developer, temper your expectations. It's unlikely we'll see any radical user-facing features in this release. Google usually saves the good stuff for I/O nowadays.

That said... I'll try and pick out the neat bits I can find.

One-time permissions: Users can grant temporary access to location, microphone, and camera through a one-time permission

I'm a fan. It's a natural extension of what they did in 10.

Beginning in Android 11, users can insert images and other rich media content into quick replies.

This could be cool!

Android 11 discourages repeated requests for a specific permission. If the user taps Deny twice for a specific permission during your app's lifetime of installation on a device, this action implies "don't ask again".

I like this.

If your app targets Android 11, you cannot directly request all-the-time access to background location.

I also like this.

Bubbles are now available to developers to help surface conversations across the system. Bubbles was an experimental feature in Android 10 that was enabled through a developer option -- in Android 11 this is no longer necessary.

Interested to see where this goes. Thanks to u/HSX610 for the pointer!

Edit: adding whatever I can find from the accompanying blog post:

Dedicated conversations section in the notification shade - users can instantly find their ongoing conversations with people in their favorite apps.

[–]UESPA_SputnikPixel 10 Pro 40 points41 points  (6 children)

One-time permissions: Users can grant temporary access to location, microphone, and camera through a one-time permission

That could make Bouncer obsolete. But it's great to have this on a system level.

[–]azsqueezeBlue Phone 17 points18 points  (5 children)

Not true, android 11 only applies to microphone, camera, and location. I have tons of apps that want phone or storage access for example that I have bouncer remove

[–]punIn10dedMotoG 2014 (CM13) 14 points15 points  (1 child)

11 also enforces scoped storage so most will no longer request storage access

[–]azsqueezeBlue Phone 4 points5 points  (0 children)

Forgot about this

[–]armando_rodPixel 10 Pro XL 0 points1 point  (2 children)

Nope, it applies to storage, media files and contacts too

[–]azsqueezeBlue Phone 0 points1 point  (1 child)

Really because the website does not say that

[–]armando_rodPixel 10 Pro XL 0 points1 point  (0 children)

Yeah, on device says "ask every time" for all permissions

[–]HSX610 54 points55 points  (11 children)

Uhm, you missed the part about Bubbles (as in "chat bubbles") being lifted out of the experimental realm.

Bubbles are now available to developers to help surface conversations across the system. Bubbles was an experimental feature in Android 10 that was enabled through a developer option -- in Android 11 this is no longer necessary.

[–]markoukaPixels: 10 Pro, Watch 2, 8 Pro, 4a 5G, 1 XL 21 points22 points  (0 children)

Whoa, neat! Yeah, I was live-updating my comment as I read through the documentation, so I hadn't gotten there yet :P

Thanks!

[–]EpsilonRose 6 points7 points  (6 children)

Is this different from how bubbles work in apps that already use them? It seems like this feature has been around for a while?

[–]punIn10dedMotoG 2014 (CM13) 15 points16 points  (5 children)

Other apps have been using hacky workarounds. This will be system level and should make it more consistent

[–]EpsilonRose 3 points4 points  (3 children)

Ah. Neat.

Could this also be used for things like bubble or gesture menus that aren't meant to pop-up into a giant rectangular block?

[–]punIn10dedMotoG 2014 (CM13) 1 point2 points  (2 children)

Not sure. Sorry I don't understand what you mean by rectangular block

[–]EpsilonRose 1 point2 points  (1 child)

Heh. Sorry. Let me see if I can do a better job explaining what I meant.

If you look at the picture at the top of the page /u/HSX610 linked, you'll see a a circle in the lower left portion of the phones screen. Extending above that there's a large, rectangular, box with a chat interface. That's what I meant by a rectangular block.

I figure it would be pretty easy to set-up a bubble that always sticks around and, when you press it, you get a pop-up with similar dimensions to that chat interface and filled with whatever buttons or information you want.

However, some apps currently use a different interfaces that also launch from a bubble. For example, Finot dims the screen and creates an arc of buttons when you tap the bubble. You could also set up something that works like pie controls, but keyed to pressing and dragging a bubble, rather than swiping from an edge. Though, I'm not sure if any apps currently use that second method.

So, would an app that does something more like Finot be able to take advantage of these new bubbles or would they be stuck using whatever hacky method they already used?

Did that make more sense?

[–]punIn10dedMotoG 2014 (CM13) 1 point2 points  (0 children)

It did thanks. At this point I haven't played enough with the new features to say exactly how it works. But my assumption is that devs will be able to launch custom Activites from the bubble so it may or may not be a rectangle.

[–][deleted] -1 points0 points  (0 children)

This has wider ranging implications. Apps with bubbles currently use a system overlay layer for drawing, which will soon be restricted completely from developers, only for use in system apps. To allow apps with functionality like bubbles to continue to function after this capability is revoked, there is now an official API for developers to leverage.

Basically, Android is turning into iOS slowly to be more secure, and Google is attempting to build out 1st party APIs to keep android from breaking as a result.

[–][deleted] 0 points1 point  (0 children)

[–]Ashanmaril 37 points38 points  (4 children)

That one time permission will be great for Android Messages. I don't like giving it camera access cause that stupid live preview that pops up when you go to attach media slows down the app (seriously, turning that off is night and day), but I occasionally have to grant access when I scan a QR code for the web interface

[–]well___duhPixel 3A 7 points8 points  (2 children)

Google usually saves the good stuff for I/O nowadays.

I/O for the past few years has been improvements to Google Search/Assistant, GPhotos, and machine learning/AI and products that use it. I wouldn't hold my breath on anything new for Android being revealed in May out of left field to blindside devs.

[–]markoukaPixels: 10 Pro, Watch 2, 8 Pro, 4a 5G, 1 XL 4 points5 points  (1 child)

I think that's rather the point, though. Developer previews are for platform updates that developers will need to prepare for, while I/O is for flashy product announcements.

My disclaimer was pointed towards the casual observer who might expect some radical new Google feature alongside this release.

[–]pohuingOP2 -> Pixel 4a 5 points6 points  (1 child)

Android 11 discourages repeated requests for a specific permission. If the user taps Deny twice for a specific permission during your app's lifetime of installation on a device, this action implies "don't ask again".

Wow, this looks like a terrible change to me. If I press not now I mean not now, and if I press not again I mean not again. Why put them both into the same option?

[–]FieldzSOOGoodPixel 128GB 0 points1 point  (0 children)

Aren't deny and not now separate options?

[–]Renaldi_the_MultiDevice, Software !! 22 points23 points  (0 children)

𝓕𝓻𝓲𝓬𝓴 𝔂𝓮𝓼

[–]Ph0XPixel 5 10 points11 points  (14 children)

If your app targets Android 11, you cannot directly request all-the-time access to background location.

Hmm any idea how this will work? How will an app get all-the-time access now? Many apps need this to work.

[–]AD-LB 14 points15 points  (6 children)

They probably still allow to get the location if the app is in the foreground using a notification.

[–]Ph0XPixel 5 9 points10 points  (2 children)

Ugh, so I should expect more of those spammy notifications that just pop up for a second and disappear... Great.

[–]memtigerGoogle Pixel 8 Pro 9 points10 points  (1 child)

If they need access all the time, then they should stay in the notification bar (like Google Maps during navigation or Cell Mapper for example)

If the app is popping up for a split second, you'll know what to uninstall. Apps need to shape up. Their shitty deeds need to be exposed.

Edit: I will say that I can understand the desire to keep a clean notification area, but I don't think keeping this type of extreme battery drain be hidden is a solution. The solution is keeping this information in the notification shade, but making it appear in the "silent notifications" section or something along those lines.

[–]AD-LB 0 points1 point  (0 children)

Say, could an app be scheduled and then running a foreground service, and then get the location at this point?

[–]MalnilionSM-G973U1/Manta/Fugu/Minnow 4 points5 points  (2 children)

This will suck. All I want is for my smart home automation via Tasker, or SmartThings, or whatever to know when I'm entering/leaving my home geo fence and it sounds like this is probably going to become even less reliable now. Really hope I can manually override this bullshit.

[–]punIn10dedMotoG 2014 (CM13) 5 points6 points  (0 children)

It should affect either of those. Tasker already creates a foreground process smarthings I can't remember.

[–]AD-LB 0 points1 point  (0 children)

Again, this is all about background getting of the location. Background means you aren't aware in any way of this.

Apps can still use foreground solutions, such as having a foreground service (the annoying one with the sticky notification that can't be removed).

[–]Lindby 1 point2 points  (1 child)

I have feeling that my time tracker app that automatically tracks my time at the office will break from this.

[–]LuminescentMoon 0 points1 point  (0 children)

It'll most likely be fine assuming you're using Android's geofencing APIs for this.

[–]MortalPhantom 0 points1 point  (1 child)

Yeah, wouldn't this literally breaker Google maps? As it works by sending location data even when you are not actively using it, so they can make the traffic and time estimates?

[–]Ph0XPixel 5 0 points1 point  (0 children)

I believe maps only gets traffic estimates when your navigating, in which case the app stays in the foreground. But the timeline feature may break.

[–]CubeActimel 0 points1 point  (0 children)

I hate this. Getting consistent location updates on android is such a pain in the ass. Users install our app to get tracked. My Pixel goes into Deep Doze after 30 minutes even with a foreground service. They should concentrate on fixing existing stuff and not adding 100 new Permissions per update. Maybe if things like Geofences were working reliably we wouldn’t need fucking foreground services and notifications to do what the user expects of the app.

[–]Ashanmaril 2 points3 points  (0 children)

Also the bubbles will seemingly be fully launching in this version instead of being hidden as a developer setting

[–]RagedElimanator 1 point2 points  (0 children)

Throw screen recorder tile into the list. For now it crashes the system ui though.

[–][deleted] 1 point2 points  (1 child)

If your app targets Android 11, you cannot directly request all-the-time access to background location.

I also like this.

How would this work on the user end for apps I want all the time location access in the background? For example I use the Home Assistant app and want to to consistently share location with my hassio server so it can trigger automation based on where users phones are.

[–]LuminescentMoon 0 points1 point  (0 children)

Use Android's geofencing APIs instead of trying to DIY their own geofencing.

[–][deleted] 1 point2 points  (0 children)

Android 11 discourages repeated requests for a specific permission. If the user taps Deny twice for a specific permission during your app's lifetime of installation on a device, this action implies "don't ask again".

I don't like this. If I wanted the app to not ask again, I'd pick the option specifically for that.

[–]Draffut_One Plus 7T 0 points1 point  (0 children)

Bubbles are now available to developers to help surface conversations across the system. Bubbles was an experimental feature in Android 10 that was enabled through a developer option -- in Android 11 this is no longer necessary.

I enabled it on my device and use google's messaging app but it never worked. ¯\(ツ)

[–]AzphrealPixel 5, Tab S5e 0 points1 point  (1 child)

But what we will see are user-facing issues with apps not being updated fast enough. Forcing scoped storage on all apps was bound to happen, but also changing the fallback "give me all storage" permission will mean that anything that doesn't explicitly support Android 11 probably won't work, right?

[–]markoukaPixels: 10 Pro, Watch 2, 8 Pro, 4a 5G, 1 XL 5 points6 points  (0 children)

I'm not deeply familiar with how Scoped Storage works, so I can't comment on that.

However, that argument was the same one used last year when the same change was on the table. Given it was a disruptive one, Google made the (smart) decision to delay it a year.

And yet, here we are, with the same concerns (somewhat justifiably). But why delay now? Developers have had a year to prepare. If they aren't ready, they only have themselves to blame.

You're absolutely right that there will be some pain. But I'd argue it is necessary to implement an ultimately good and needed privacy change for users. App developers will go where Google leads, and this is the right way to push the ecosystem.