Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Onboarding screens should only appear once #4850

Open
bengtan opened this issue Feb 28, 2020 · 7 comments
Open

Onboarding screens should only appear once #4850

bengtan opened this issue Feb 28, 2020 · 7 comments
Assignees

Comments

@bengtan
Copy link
Contributor

bengtan commented Feb 28, 2020

Due to discussions at #3740 (comment) and over a voice chat meeting ... it has been agreed that the onboarding screens should only appear once.

Ideally,

  1. It should only appear once per new user

but it might be more practical to do:

  1. It should only appear once per new install.

(I'll leave the discretion to the developer.)

@southerneer
Copy link
Contributor

It has to be per install, because we can't turn on permissions for an existing user if they install the app on another device.

@southerneer
Copy link
Contributor

Well, I guess we could still request the same permissions without the onboarding screens, but I think seeing onboarding on each new device is a normal experience for other apps so it shouldn't be disorienting for our users.

@mstidham
Copy link

I'm wondering if I should have waited to test this after this version but I deleted the app and reinstalled and got an app crash. I noted this on the bugsnag #4820

image

@bengtan
Copy link
Contributor Author

bengtan commented Mar 16, 2020

@mstidham:

I'm guessing that the bugsnag/crash should be unrelated to this ticket, but if it's preventing you from QA-ing this ticket, then please wait until we look into it.

@southerneer
Copy link
Contributor

@mstidham that test was with 4.41.0? What were the steps that led up to the crash? It sounds like this happened just after a fresh install...no other steps? I'm able to test this ticket successfully with the following steps...

  1. Install fresh 4.41.0
  2. login (bypass or regular)
  3. go through the onboarding screens
  4. logout
  5. login (same or different account)
  6. note that there's no need to go through the onboarding process again

@southerneer
Copy link
Contributor

Also, I think the bug referenced in that screenshot is unrelated to this ticket. It looks like #4820 could use some more work.

@mstidham
Copy link

@southerneer Verified on Staging Version: 4.41.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants