Hey everyone! 👋 I’ve been diving into authentication for a React Native app I’m working on, and I’m leaning toward Auth0 for handling social logins (Google, Apple, maybe Facebook). I love that it promises to offload a lot of the security complexity, but I wanted to check in with the community before committing.
Has anyone here integrated Auth0 into a React Native mobile app specifically? I’m curious about:
* **Real-world performance** – any noticeable latency during login flows?
* **Social login UX** – does it feel seamless, or are there hiccups with redirects or session management?
* **SDK stability** – how smooth was the integration with the Auth0 React Native library?
* **Cost at scale** – we’re starting small, but how does pricing feel as monthly active users grow?
I’ve also briefly looked at alternatives like Firebase Auth and Supabase, but Auth0’s breadth of identity providers and enterprise-friendly features keep pulling me back. Would love to hear your experiences—good or bad—especially if you’ve compared a few options. What made you choose (or avoid) Auth0 for a similar project?
Happy benchmarking!
Always testing.
I run growth for a 60-person SaaS. Our main product is a React Native mobile app. We moved from Auth0 to Supabase Auth about 18 months ago and haven't looked back.
* **Cost at scale:** Auth0's per-user pricing was unsustainable. We hit ~10k MAU and the bill was ~$750/month. Supabase Auth costs us $25/month on the Pro plan, as it's based on database usage, not active users.
* **Social login UX:** Auth0 felt slower because it opens a browser tab. Supabase uses a secure webview, which feels more native. Both work, but our drop-off during signup was about 15% lower with Supabase's flow.
* **SDK stability:** The Auth0 React Native SDK had more moving parts and we ran into occasional redirect state issues on iOS. Supabase's is a thin wrapper around their JS SDK; integration took an afternoon.
* **Where Auth0 wins:** If you need 20+ enterprise identity providers (like SAML connections to specific AD instances) and have a team to manage it, Auth0 is the clear choice. For Google/Apple/Facebook, it's overkill.
My pick is Supabase Auth for any startup or scale-up where cost and simplicity are priorities. The only reason to choose Auth0 is if you have an immediate, confirmed need for complex enterprise social logins that Supabase doesn't support.
Optimize or die.
Great point about the webview vs browser tab experience. That's something you don't really think about until you see the metrics.
I'd add one small caveat from my own tinkering. While Supabase's pricing is fantastic for predictable scaling, you do need to keep an eye on those edge cases that can drive up database operations. Things like aggressive session refresh logic or a lot of failed login attempts from a misconfigured button can creep up on you. It's still way more manageable than Auth0's model, but it shifts the cost monitoring from "users" to "activity spikes".
Have you had to implement any specific logging or alerts to watch for auth-related database load?
Spreadsheets > opinions