[nav] Refactor auth to follow design user flows

[adityapawar1]

What's new in this PR

Make the auth flow follow the Figma

Relevant Links

Notion Sprint Task

https://www.notion.so/calblueprint/nav-Refactor-auth-to-follow-design-user-flows-c792823f07484bd9a251a577a2668cb2?pvs=4

Online sources

Related PRs

How to review

You can create a temporary email here if you already have an account on your personal email.

Next steps

Tests Performed, Edge Cases

Full sign-up with a new account

Screenshots

RPReplay_Final1697504961.MP4

CC: @akshaynthakur
CC: @brendovuong

[adityapawar1]

Some weird things I wasn't to sure about:

• The sign up screen gets converted into the login screen (the button text and onPress change) after email verification
  • I couldn't find a way to sign up the user based on a callback of them verifying their email, so i just had them click log in when they're ready, but i think this could be worked on. Maybe we can use the redirect url, use the verify email with the sequence of numbers they send to your email, or a supabase trigger which might be able to trigger a callback on the app.
  • if the user changes their email after clicking sign up then the button will still say "log in" instead of "sign up" and would have to reload the page (go to login page and then back to sign up) to fix it.
• The onboarding screen says "Skip for now" even after updating details which should be an easy fix, but I'm mostly concerned about the above thing

[akshaynthakur]

One small thing, try to be a little more descriptive with your PR name as [auth] Auth flow is a little vague. You can always use the name of the sprint task from Notion, so in this case [nav] Refactor auth to follow design user flows.

[akshaynthakur]

Some weird things I wasn't to sure about:

• The sign up screen gets converted into the login screen (the button text and onPress change) after email verification

  • I couldn't find a way to sign up the user based on a callback of them verifying their email, so i just had them click log in when they're ready, but i think this could be worked on. Maybe we can use the redirect url, use the verify email with the sequence of numbers they send to your email, or a supabase trigger which might be able to trigger a callback on the app.
  • if the user changes their email after clicking sign up then the button will still say "log in" instead of "sign up" and would have to reload the page (go to login page and then back to sign up) to fix it.

• The onboarding screen says "Skip for now" even after updating details which should be an easy fix, but I'm mostly concerned about the above thing

Great callouts! We'll talk with Brenda during work session about whether a number/code entry or automatic redirect trigger makes most sense and make a decision there. We can add this to your next sprint task. I think the changing email issue should resolve itself because we'll be changing the flow of the screens.

[akshaynthakur]

Nice job reworking this flow! See my comments for some small changes as well as notes about what you'll be iterating upon next

[akshaynthakur]

Nice work!