Is it true that there are no actions for Android integrated yet to get some control over dangerous permission requests in our apps?
When I need ExternalStorage permission once in my app for a specific feature, for example - download some game resources for the first time
or create an easy accessible local backup save folder for the user, so they could easily migrate their progress to a new Android device.
For these features I definitely don't want that I can only prompt to users when the app starts, although it's not required at that point.
So without some control over these permissions, it's often hard to find workarounds for certain features to ensure a good core app quality
at any time. In Google documentation for Android app development I also found the hint:
Don't check for or request permissions when the user opens your app.
Instead, wait until the user selects or opens the feature that requires a particular permission.
A basic set of custom actions when requesting these permissions would need two important things:
- an event to request the dangerous permission
- a condition check "permission not granted by user after last request?"
And optional useful, but not absolutely necessary:
a test condition - On permission requested
(permission requested → do something, run a message for example:
"Local Backup feature unlocked - you might have noticed that the 'backup button' has now turned green - Thanks for granting!"