Integrations
Overview
The services we'll connect during onboarding and when each one matters.
Most apps we build rely on a handful of third-party services. Some are required to ship to the stores; others power features like authentication, analytics, crash reporting, or payments. This section walks through each one and exactly what we need from you.
What you'll set up
| Integration | Why we need it | When it's needed |
|---|---|---|
| Apple Developer Account | Sign and publish your iOS app | Before first beta |
| Google Play Console | Sign and publish your Android app | Before first beta |
| Firebase | Backend services: auth, database, notifications | During Build |
| Sentry | Crash and error monitoring | Before first beta |
| RevenueCat | In-app purchases and subscriptions | If you sell in-app |
How this works
Each integration page follows the same structure so they're predictable to work through:
- Why we need this — a short explanation of the service's role.
- What you'll need before starting — credentials, payment methods, business info, etc.
- Step-by-step setup — the exact clicks to create or configure the account.
- How to grant Calda access — the email, role, or token to share with us.
- Verification checklist — how we both confirm it's set up correctly.
If you've already set up some of these for a previous project, just let us know and we'll jump straight to the access step.