For months I kept LaunchAlly's authentication simple: email, password, verify your email and you're in.
It worked.
But it didn't feel great.
One thing I kept hearing was:
"Can I just continue with Google?"
So I finally implemented Google OAuth using Supabase.
It sounds like a tiny feature, but it changed the entire first impression of the product.
A few things I learned while building it:
- Google Cloud Console configuration is more confusing than the code itself.
- Redirect URLs have to match exactly.
- Supabase makes the OAuth flow surprisingly clean once everything is configured.
- Small UX changes matter much more than we think.
I also redesigned the authentication pages so the "Continue with Google" option is the primary action, with email registration below it.
The onboarding now feels significantly smoother.
Current LaunchAlly roadmap:
✅ Google Sign-In
✅ Team Workspaces
✅ Stripe subscriptions (almost finished)
🔄 Team invitations
🔄 Analyzer V4
🚀 More deployment workflows
It's always satisfying when a feature users expect becomes something they don't even have to think about anymore.
If you're building your own SaaS, I'd recommend investing in onboarding earlier than you think. A great first impression is hard to replace later.
What authentication provider do you usually implement first?
Top comments (0)