Talking about SMS/MMS, not alternative forms of messaging. You can only have one at a time, and if people want to migrate they need a way to export and import their data. Supporting that means letting people get tricked into giving it to a sketchy app.
If you want to allow more power, let app provide custom code to run in full seccomp processing camera stream with small-N byte limit to send back when done.
-
-
Agree, and the situation is that these existing operating systems / APIs with massive app ecosystems are here and they need to be slowly moved towards approaches like that via incredibly painful ecosystem-wide breaking changes with each major release.
-
Fully expect that stuff like persistent, bulk access to pictures, etc. gets mostly or entirely phased out. It's a painful, long process. Google eventually implements a fair number of the things that we implemented earlier and never expected them to provide any time soon.
-
It's a lot harder for them to do a lot of the things we decide are good ideas and implement downstream. Sometimes they make features for us and don't deploy them, like legacy app permissions review (we don't grant those at install time and we don't silently disable by default).
-
Permissions review == when you first run a legacy (API <= 22, i.e. not updated for post-5.x era APIs) app, you're shown toggles for all the permissions instead of them being enabled by default. It's a standard AOSP feature, not something we made. We only made some tweaks to it.
-
Earlier, we offered an opt-in option to disable permissions for legacy apps by default, but that wasn't very usable at all. Certainly not usable enough for us to enable it by default, and not enabled by default effectively means useless since few people will actually use it.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.