Firebase
Backend services for authentication, database, storage, and push notifications.
Why we need this
Firebase powers many of the runtime features in your app: authentication, the realtime/Firestore database, file storage, push notifications, and analytics. We need a project that's owned by you so the data and billing stay under your control, with Calda added as an editor.
Step-by-step setup
Create the Firebase project
Go to console.firebase.google.com
and sign in. Click Add project, name it (e.g., your-app-prod), and
disable Google Analytics for now unless we've discussed otherwise.
TODO: decide whether to start on the Spark (free) or Blaze (pay-as-you-go) plan with your project lead. Most production apps end up on Blaze.
Register iOS and Android apps
Inside the new project, add an iOS app and an Android app using the bundle ID / package name we shared with you.
Download the configuration files (GoogleService-Info.plist and
google-services.json) — we'll need them in the next step.
Share the config files securely
Send the downloaded config files to Calda via a shared vault (1Password, Bitwarden, or similar) — not Slack DM.
(Optional) Upgrade to the Blaze plan
If we'll be using Cloud Functions, upgrade the project to the Blaze plan from Usage and billing and set a budget alert.
Invite Calda
Open the Firebase Console, click the gear icon → Users and permissions, then click Add member. Enter the Calda email we share with you and assign the Editor role.
We'll confirm in Slack that we can access the project.