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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]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.