There are several ways to manage permissions. You can always activate the permission later if you need it. If a developer doesn’t bother explaining what the permission will be used for, and you don’t see why it’s useful, say no. Unless you want to be pestered by that game, just say no. For example, you might open a mobile game and immediately see a request to send you push notifications. If you disagree, the app can never ask for this permission again - this avoids the problem of an app repeatedly asking permission to do something you don’t want it to do. You can still give the app the permission afterwards, but you’ll have to visit the system Settings screen. If you agree, the app will have the permission forever - or until you remove it yourself. This gives you an idea of why exactly an app will need that permission, and you’ll see the system permission prompt. Apps are often set up to explain why they’ll request the perimssion. For example, an app might only request access to your photo library when you try to attach a photo. Typically, a well-designed app will ask for permission before it does something that will require the permission. RELATED: iOS Has App Permissions, Too: And They're Arguably Better Than Android's
0 Comments
Leave a Reply. |