Android: Rephrase "Lock" term to make it clearer that it is a app access restriction

Created on 5 Jul 2018  Â·  3Comments  Â·  Source: nextcloud/android

see https://help.nextcloud.com/t/android-client-pin-fingerprint-protection-pointless/33590/2

The thread shows that the access restriction we have is/can be misinterpreted as a file access restriction while it is a app access restriction. So I think we should thus show this fact as in maybe renaming "Lock" to "App access restriction" or something like that. Not a native speaker so maybe @nextcloud/designers or @mario @tobiasKaminsky have a better term to be used here :)

approved design enhancement good first issue

Most helpful comment

I would say "App passcode". Because stuff like "App protection" or "App security" with "none" below it seems strange. ;)

The text below should reflect the currently enabled passcode method like it is now.

(Yes, when it’s set to passcode it will say "App passcode" and below "Passcode", but I’d say that’s ok?)

All 3 comments

To make it a bit clearer what we are talking about (for others):

This protects the app from starting without entering correct pin/device credentials (fingerprint, password, …).
It is not meant to protect downloaded files on internal storage.

2018-07-05-142954 2018-07-05-142957

Suggestion:

  • app protection
  • App lock
  • Lock, but with a text "prevents unauthorized people from using app"

I would say "App passcode". Because stuff like "App protection" or "App security" with "none" below it seems strange. ;)

The text below should reflect the currently enabled passcode method like it is now.

(Yes, when it’s set to passcode it will say "App passcode" and below "Passcode", but I’d say that’s ok?)

Sounds good to me :+1:

Was this page helpful?
0 / 5 - 0 ratings

Related issues

tobiasKaminsky picture tobiasKaminsky  Â·  3Comments

tobiasKaminsky picture tobiasKaminsky  Â·  3Comments

AndyScherzinger picture AndyScherzinger  Â·  3Comments

daywalk3r666 picture daywalk3r666  Â·  3Comments

JSoko picture JSoko  Â·  3Comments