3 ms·
> There is nothing that can be done from the system's point of view for that. They can ban the app from app stores for using any non-system interface to reques
by hctaw 5y ago
> There is nothing that can be done from the system's point of view for that.
They can ban the app from app stores for using any non-system interface to request permissions, like they do for payments.
- MrDresden 5y agoI am not agreeing with it, but they are showing a piece of custom ui that probably links into the settings for you to make changes. That is a very normal practice on Android. The fact that Snapchat decides that pestering the user for the permission is acceptable I find to be a very strange design decision.
- hctaw 5y agoIt's not that strange, it's just a dark pattern. But it does touch on a specific problem with permissions interfaces. If you have an interface that looks like "requestPermissions(...)" or something like that and have a case where users can reject permissions forever without nags, then how do you handle users who inadvertently deny permissions forever? One solution is to just nag forever, if you can. Another workaround is to enable permissions manually through settings, but you need to make errors loud and obvious with workaround instructions and people interpret the issue as a bug in your code rather than a feature of the platform. This is a problem on MacOS, just as an example.