-
Notifications
You must be signed in to change notification settings - Fork 22
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
Frictionless Adoption: Anonymous Timers? #58
Comments
Steps:
|
We are going to use localStorage on the client/browser to store the (session) token. |
This is working. Need to put it in practice to iron out any kinks. |
@nelsonic On a non-technical note, should we allow anonymous (unregistered people) to have more than one timer (i.e. stop a timer and start a second, third or fourth one, etc) before they have to register to save their timers? |
That question should not be directed at "just" me... But letting anonymous people start multiple timers it really a question for discussion and deserves its own issue... @iteles want to open an issue dedicated to discussing it? 😉 |
@iteles what else do we need to do to close this? have you tried the latest alpha itteration which allows people to start/stop as many timers as they want and then transfer these timers to their account once they register...? what else...? |
Anonymous timers work 👍 We just need to test #91 and we can wrap on iteration 1 of anonymous people functionality I reckon. |
To _minimise adoption friction, when a person first arrives on the site/app we should allow them to try starting timer(s) _without registering or logging in. This means they are anonymous to us. 😮
To make this work we need to assign them a JWT they can use to interact with the app anonymously.
if they decide to register their email address (and thus keep their timer(s) securely saved) their timer(s) will be owned by the email address they register with.
The text was updated successfully, but these errors were encountered: