Skip to content

Permission Screens

Jump to bottom
Insa Suchantke edited this page Jan 29, 2020 · 11 revisions

Permissions

  • CALL_PHONE
  • Storage
    • READ_EXTERNAL_STORAGE
    • WRITE_EXTERNAL_STORAGE
  • Bluetooth
    • BLUETOOTH
    • BLUETOOTH_ADMIN
    • ACCESS_FINE_LOCATION

Text CALL_PHONE

Im Folgenden benötigt die App einige Zugriffsberechtigungen. Falls es Ihnen nicht gut gehen sollte, können Sie im Notfall mit Hilfe der App eine Person anrufen, deren Nummer Sie vorher eingespeichert haben. Dafür benötigt die App Ihre Erlaubnis, jemanden anzurufen. Die App verwendet nicht Ihr Telefonbuch.

Text STORAGE

Die App erfasst auch Ihre Gesundheitsdaten, damit sie Ihnen Informationen über Ihre Gesundheit geben kann. Zur Speicherung Ihrer Daten benötigen wir Ihre Erlaubnis, dass diese Daten auf Ihrem Handyspeicher gespeichert werden können.

Text BLUETOOTH

Zur Erfassung Ihrer Gesundheitsdaten wird die Waage mit Ihrem Smartphone über Bluetooth verbunden. Dafür wird der Zugriff auf Ihren Standort benötigt, damit die Verbindung funktionieren kann.

(TODO: information why location is used is missing -> "The other permission that you must declare is ACCESS_FINE_LOCATION. Your app needs this permission because a Bluetooth scan can be used to gather information about the location of the user. This information may come from the user's own devices, as well as Bluetooth beacons in use at locations such as shops and transit facilities." see android doku)
(TODO: there is some more information about permission handling, probably most is redundant)
(TODO: here is more information about permission requests and grouping of permissions, maybe add that information in here)

Permissions usage

Be transparent

  • When you make a permissions request, be clear about what you’re accessing, and why, so users can make informed decisions.
  • Make this information available alongside the permission request including install, runtime, or update permission dialogues.

Explain why you need permissions

  • The permissions dialog shown by the system when you call requestPermissions() says what permission your app wants, but doesn't say why.
  • It's a good idea to explain to the user why your app wants the permissions before calling requestPermissions().
  • Research shows that users are much more comfortable with permissions requests if they know why the app needs them.
  • As a result, if you’re only using a fraction of the API calls that fall under a permission group, it helps to explicitly list which of those permissions you're using, and why.

The right way to ask for permissions

  • Permission strategy depends on the clarity and importance of the permission type you are requesting.
  • Critical permissions should be requested up-front, while secondary permissions may be requested in-context.
  • Takeaway: Make sure the user clearly understands what the app does (based on app’s description or previous familiar experience) and ask up-front only critical permissions which user expect the app to request.

How to ask the user

  • Apps should clarify why each permission request is needed, either through the feature name or an explanation provided.
  • Remember, if you want to get a Yes answer, you have to ask nicely.
  • A simple rule: Make sure it’s crystal clear for users what they’ll get in return for accepting the request.

Clone this wiki locally