Firebase Auth
Firebase Authentication is Google's sign-in service for apps, and I use it in projects that already run on Firebase.
How I use Firebase Auth
It handles email and password or Google sign-in, and Firebase stores passwords and sessions, so the app doesn't have to manage that sensitive part itself.
You get a proven sign-in flow without storing passwords yourself: password reset, email verification and basic abuse protection are built in. If the app already lives on Firebase, sign-in fits in without moving to another system.
When I use it, I track the sign-in state in the app, protect pages meant for signed-in users, and write Firebase Security Rules that check who the user is, not just whether they're signed in. I don't have a portfolio project where Firebase Auth is the main solution, so I count it among the tools I use less often.
For new systems I usually choose Supabase Auth, because users and access rules sit in the same PostgreSQL database as the data. Firebase Auth remains a sensible choice when a project already uses Firebase Hosting and Firestore.
Frequently asked questions about Firebase Auth
What is Firebase Authentication?
Firebase Authentication is a Google service that gives apps ready-made user sign-in: email and password, phone, Google and other accounts. Firebase stores passwords and sessions, so developers don't have to build that part themselves.
Firebase Auth or Supabase Auth: which should you choose?
Firebase Auth fits naturally with Firestore and the rest of Firebase, while Supabase Auth ties users to a PostgreSQL database and RLS policies. If an app already runs on Firebase, I stay with Firebase Auth; for new systems I usually choose Supabase Auth.
Do you set up user sign-in with Firebase?
Yes, when a project is already on Firebase, but it isn't my main solution and I don't have a portfolio project built on Firebase Auth. For new systems I usually choose Supabase Auth, since users and access rules live in the same database as the data.