Please enable JavaScript.
Coggle requires JavaScript to display documents.
RwA Sprint 1 (Initial priorities for the app to be usable and consistent…
RwA Sprint 1
Initial priorities for the app to be usable and consistent
Sign up/in with Auth0
Onboarding process on first time login
build new design into logged out landing (very basic one - no nav except login/signup, no blocks, no footer etc)
build new design into dashboard (again very basic - only what currently exists but using new style)
build new design into 'create room' page (modal instead)
build new design into 'join room' page (modal instead)
build new design into choose book component
build new design into reading room page
build new design into 'you've left the reading room' page
build 'allow audrey to access microphone' step before reading room loads
User can sign up
Build sign up page
Look to other's code to see how it is working
Need to get login details for all the tools beng used on the FAC website
Is this sign up process going to work the same as it is currently?
When is user going to put in their details? After they have signed up with Auth0?
Sign up with Auth0 -> redirect to app -> trigger onboarding
Time estimate: 5 days
Build modal for example bio
Edit Auth) to allow sign up as well as login
Send user details to prefill onboarding form
User can view a dashboard
can see current reading rooms
can create/join reading rooms
can see completed readings
User can login
Build new login page
Time estimate: 2 hours
User can read about Audrey
build about page
Time estimate: 1/2 day
User can read FAQ's
0.5 days
User can get in touch
0.5 days
User can create a reading room
User can join a reading room that exists already
User can see how many sessions they've completed in each room