The answer
Because auth depends on authorized domains configured in the auth provider. Auth that works on localhost can fail in production if you forget to add your deployed domain. Always test the full auth flow on the deployed app.
Roadmap: Finishing and Shipping a React Project
Why confirm auth in production specifically?
More FAQs in Roadmap: Finishing and Shipping a React Project
In order: polish the UI, add loading and error states everywhere, confirm auth works in production, run the production build, set environment variables, deploy, test the deployed app, then monitor and iterate.
Polish the UI. Run through the app and refine spacing, colors, hover states, and transitions. Test on mobile and desktop, on real devices where possible, so the app feels finished, not just functional.
Because some issues only appear in production, like wrong environment variables, unauthorized auth domains, or broken deep links. Testing on the deployed app catches these before users do, which is the point of finishing.
Still have questions?
Browse all our FAQs or reach out to our support team
Want to upskill yourself?
Your learning library
Small steps. Big possibilities.
Find your next course. Build something great.