Firebase Launch Checklist

This document contains a checklist of things to consider before launching a Firebase app to production.

Update your connected apps

Android Add a release SHA-1 hash for your app's signing certificate in the Project settings of the Firebase console (for OAuth client IDs). This is required if your app uses Firebase Authentication (Google sign-in or phone number sign-in) or Firebase Dynamic Links.

iOS Update your App Store ID and Bundle ID and Team ID (if necessary) in the Project settings of the Firebase console.

Web Add whitelisting for your domains to prevent unauthorized usage.

  • Whitelist your production domain for browser API keys and client IDs in the Google Developer Console.
  • Whitelist your production domain in the Auth tab of the Firebase console panel.

Know your plan limits and set budget alerts

All The Realtime Database, Storage, and Hosting features have hard usage caps on the Spark and Flame plans. Hitting these limits may mean that your app stops working as you intend. Consider upgrading to the Blaze plan to remove these limits. See the pricing page for more details.

All Set up budget alerts for your project in the GCP console.

All Monitor your Usage and billing dashboard in the Firebase console.

Prepare services

Analytics

All Define audience parameters for Analytics to start collecting users from launch.

All Upload proguard files for release builds for use in Crashlytics.

All Enable BigQuery linking if you plan to use BigQuery with your Analytics data.

Authentication

Android Configure your proguard rules to work with Authentication.

Android Add a release SHA-1 hash for your app's signing certificate in the Project settings of the Firebase console (for OAuth client IDs). This is required if your app uses Google sign-in or phone number sign-in.

iOS Ensure you have error handling on iOS for common errors.

All Disable providers you aren't using (especially anonymous users in Firebase console).

All If using Google Sign In, personalize your OAuth consent screen.

All Customize your domain and sender for the Authentication email sending service.

Cloud Firestore

Android Make sure your release build uses ProGuard for code shrinking. Without ProGuard the Cloud Firestore SDK and its dependencies can add as much as 1MB to your APK size.

All Configure your Security Rules to prevent unintentional data access.

Cloud Messaging

iOS Be sure to upload your APNS Auth Key for Cloud Messaging on iOS in the Firebase console. If using APNS certificates, ensure that your production APNS certificate is uploaded.

All Enable BigQuery linking if you plan to use BigQuery with your Cloud Messaging data.

Cloud Storage

All Configure your Storage Security Rules to prevent unintentional data access.

Crashlytics

Android Upload proguard mapping for release builds for use in Crashlytics.

iOS Upload dsym file for release builds for use in Crashlytics.

All Enable BigQuery linking if you plan to use BigQuery with your Crashlytics data.

Android Add a release SHA-1 hash for your app's signing certificate in the Project settings of the Firebase console (for OAuth client IDs).

ML Kit

Android See Prepare your ML Kit Android app for production.

iOS See Prepare your ML Kit iOS app for production.

Predictions

All Enable BigQuery linking if you plan to use BigQuery with your Predictions data.

Realtime Database

Android Configure your proguard rules to work with the Realtime Database.

All Configure your Realtime Database Rules to prevent unintentional data access.

All Ensure you're ready to scale. The Realtime Database has default quota large enough for most applications, but some apps may need extra capacity.

Remote Config

All Ensure any experimental Remote Config rules don't affect your release users, and that appropriate defaults are distributed in your app.

Release

Android Run Android apps through Test Lab to check for last minute bugs.

All Create Dynamic Links for key new features to use in promotional material and social media.