You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 12, 2021. It is now read-only.
uPort doesn't allow the user to proceed to set up his account without a security passcode on his phone.
Describe the solution you'd like
Allow users to use the app with their chosen security profiles.
Describe alternatives you've considered
Additional prompts could include: a "skip" confirmation where they agree that they are taking a risk by not locking their phone; and/or a red mark somewhere to let them know as long as they are running "insecure".
Additional context
A group is using uPort and one person does not want to set a passcode on his phone; since we're just experimenting with uPort, I agree with him that it's unreasonable to force him to change his setup just to try out this new technology. Cryptocurrency wallets used to do this same thing with the seed phrases, forcing them to confirm their phrase before continuing, but that's a barrier to adoption when we want to get someone started with $1 worth of currency (especially when working with a whole group of people)... it's just not reasonable to go through all the headache when you're trying to illustrate or analyze a new app, so that should wait until the user decides that their data is important to secure properly.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
uPort doesn't allow the user to proceed to set up his account without a security passcode on his phone.
Describe the solution you'd like
Allow users to use the app with their chosen security profiles.
Describe alternatives you've considered
Additional prompts could include: a "skip" confirmation where they agree that they are taking a risk by not locking their phone; and/or a red mark somewhere to let them know as long as they are running "insecure".
Additional context
A group is using uPort and one person does not want to set a passcode on his phone; since we're just experimenting with uPort, I agree with him that it's unreasonable to force him to change his setup just to try out this new technology. Cryptocurrency wallets used to do this same thing with the seed phrases, forcing them to confirm their phrase before continuing, but that's a barrier to adoption when we want to get someone started with $1 worth of currency (especially when working with a whole group of people)... it's just not reasonable to go through all the headache when you're trying to illustrate or analyze a new app, so that should wait until the user decides that their data is important to secure properly.
The text was updated successfully, but these errors were encountered: