Version login code and tests together
Connect
SPIRITT
FirebaseFirebase sign-in
Built for your users
SPIRITT builds login experiences around Firebase Authentication, from password and provider sign-in to session renewal. Turn authentication failures into tested fixes without treating client access as project administration.
What you can do with Firebase.
Working login journeys
Build password, email-link, and configured provider sign-in experiences that carry users from authentication to the right app screen.
Sessions that recover
Handle Firebase token renewal and expired credentials with clear recovery paths instead of unexplained login loops.
Clear authentication boundaries
Validate reset codes and inspect public project configuration while keeping admin operations and sensitive tokens out of support workflows.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the app login experience or authentication operation you want built and maintained.
02
Connect Firebase
Connect with your Firebase Web API key. Provide authorized test accounts or flow-specific credentials for the sign-in journeys you want to run.
03
Delegate an outcome
Ask SPIRITT to build a login flow, test session renewal, or resolve authentication failures with a finished interface and verified results.
Hand over a mission.
Choose a mission. Make it yours.
Put Firebase to work.
Make every sign-in count
Questions
Firebase, with SPIRITT.
01Which Firebase capabilities can SPIRITT use here?+
This connection covers Firebase Authentication client operations: public project configuration, sign-in method discovery, password sign-in, email-link completion, configured identity provider sign-in, custom-token exchange, token refresh, and password-reset code validation. It does not provide Firestore, Realtime Database, Hosting, or user administration.
02What access does a Firebase mission need?+
The connection uses a Firebase Web API key. Actual authentication also needs inputs for the chosen flow, such as an authorized user's credentials, a delivered email-link code, provider credentials, or a custom token from a trusted server. The key alone does not grant account access or administrative control.
03Can SPIRITT run recurring authentication checks?+
Yes. SPIRITT can operate scheduled password sign-in and token-renewal checks with dedicated test accounts, retain redacted results, and coordinate failures through Slack or an issue tracker. Test credentials and session tokens should remain outside reports and diagnostic logs.
04Can it build login experiences across our other tools?+
SPIRITT can build a portal login, provider callback, email-link return page, or session-renewal component. GitHub can hold the app and tests, Linear can track reproduced failures, and Google Sheets can hold environment mappings and acceptance results. Each login flow still uses its required Firebase credentials or codes.
05Does verifying a reset code reset the password?+
No. Verification checks the password-reset OOB code and returns its associated email and request type without changing the password. SPIRITT can build a validation page and route users into your existing reset-completion flow. Sending recovery emails and submitting a new password are not included in these operations.
06Can sign-in discovery tell us whether every email has an account?+
No. Firebase anti-enumeration settings can suppress sign-in method discovery results. SPIRITT can use returned methods to guide login choices, but an empty result must not be treated as proof that an account is absent. A neutral fallback keeps the interface useful without turning it into an account lookup service.