On this page
The working demo is not the launch.
Firebase prototypes can move fast, but production risk often lives in open security rules, missing indexes, mixed development and production projects, unverified Auth domains, App Check gaps, or Cloud Functions behavior that only fails after deployment.
Check Firebase before public launch
- 1Confirm development, staging, and production Firebase projects are separated where needed.
- 2Review Firestore, Realtime Database, and Storage rules alongside the data model.
- 3Verify Auth domains, OAuth provider settings, App Check, SMS abuse protection, and custom domains.
- 4Check indexes, Cloud Functions, scheduled jobs, environment config, and deploy scripts.
- 5Test production rules and the first-user path against the production project.
- 6Ask your coding agent to fix one Firebase launch gap with verification steps.
Browse all launch guides · Read resources · How to make and check your next change
FAQ for builders before launch
What should I check before launching a Firebase app?
Check security rules, Auth domains, App Check, indexes, functions, environment config, project separation, and production rule tests.
Are Firebase API keys secret?
Firebase API keys identify the project, but access control comes from Security Rules and server-side checks. Production readiness still requires rule review and provider settings.
How does VibeRaven help with Firebase launch readiness?
It does not. VibeRaven 1.7.8 has no Firebase check; it is for AI-built apps on Vercel + Supabase.