Improve UX flow
Closed this issue · 7 comments
Yush G, [2024-03-27 09:41]
Also the sign in button should probably be on the main upload screen
Yush G, [2024-03-27 09:42]
And after that start should be the main button shown and be more prominent, and everything below only shown once start is clicked
Yush G, [2024-03-27 09:42]
Basically lead the users through a flow where it's clear what to click next
@Divide-By-0 I updated the flow a bit. I hope it made it a little more intuitive for the user.
When the user is signed out, the upload page now looks like this:
When the user didn't give the full scope access:
When the user is signed in, but has not started the upload:
After the user clicked start:
And a question, Maybe the text marked in the screenshot is a bit too technical to be where it is? I added it upon request because some users were concerned, but with the new flow it seems a bit out-of-place. Any opinion on this? Should we move it to the privacy policy or something?
@Divide-By-0 All feedback is welcome!
Hey! These improvements are great. One note I would add is to say, until google has verified our account, you'll have to manually click proceed then continue.
Maybe here, you can say that email access tokens are only stored on the user's browser, the server does not store any tokens nor access any private email data. And these first 2 sentences about oauth 2.0 and jwts can move to the privacy policy, and hyperlink to that from here?
Yush G, [2024-04-01 10:22]
also for the manual flow, can you add full instructions i.e. click exactly these buttons to send the gmail email, receive an email with exactly this title, and exact instructions for what to do once you’ve got the email etc. and also that you only have 1 week after they send the email to download ur data
I updated the page a bit.
I assumed that by "you'll have to manually click proceed then continue" you referred to the step in the Google login flow, that has the option to "Go to DKIM Lookup (unsafe)".
This is how it looks now
Regarding:
the server does not store any tokens nor access any private email data.
Note that while the server does not store any tokens, it does have access to private email data, because it's the server that parses the email headers here