Publishing

Publishing is the final stretch of the project pipeline. By the time we reach this page, your integrations should be set up and the app should be running cleanly in TestFlight and Play Console internal testing. This checklist makes sure nothing slips through the cracks before submission.

Pre-publish checklist

App assets

• App icon at all required sizes (Calda generates from a single 1024×1024 master).
• Screenshots for every required device class — at minimum 6.7" iPhone, 6.5" iPhone, 12.9" iPad (iOS) and phone + 7" tablet + 10" tablet (Android).
• Preview video (optional but recommended) — 15–30 seconds, no external watermarks.
• Feature graphic for the Play Store (1024×500 PNG/JPG).

Store metadata

• App name matches across both stores and your marketing site.
• Subtitle / short description is finalized and under each store's character limit.
• Long description is proofread, formatted, and translated for any target locales.
• Keywords (iOS) are chosen with input from your project lead.
• Category and content rating are set correctly on both stores.
• Support URL, marketing URL, and privacy policy URL are live and reachable.

Legal and compliance

• Privacy policy covers every SDK in the app (Firebase, Sentry, RevenueCat, analytics, etc.).
• Apple data privacy questionnaire is filled out in App Store Connect.
• Google data safety form is filled out in Play Console.
• Export compliance answered (almost always "uses standard encryption only" for our apps).
• If using in-app purchases: products are approved and pricing is configured in all target regions.

Build quality

• All P0 and P1 bugs are closed in the tracker.
• Crash-free rate in Sentry is above 99.5% across the last beta week.
• Manual QA pass signed off by both Calda and your team.
• Analytics events verified firing correctly in production builds.
• Deep links / universal links tested on both platforms.

Submission flow

iOS (App Store)

1. Upload the production build via Xcode or our CI pipeline.
2. In App Store Connect, attach the build to a new app version.
3. Fill in What's New in This Version notes.
4. Submit for review — expect 24–72 hours for the first review of a new app, faster for updates.
5. Once Ready for Sale, schedule the release or release immediately.

Android (Play Store)

1. Upload the production AAB to the Production track in Play Console.
2. Fill in the release notes for the version.
3. Submit for review — expect a few hours to a few days depending on account history.
4. Once approved, the release rolls out at the percentage you set (we recommend starting at 20% and ramping up).

Post-launch monitoring

For the first 72 hours after launch, we actively watch:

• Sentry for any spike in crashes or errors.
• Firebase / analytics for unexpected drop-offs in onboarding.
• App Store and Play Store reviews for early user reactions.
• RevenueCat (if applicable) for purchase or subscription failures.

If anything trends in the wrong direction, we agree on a fix-or-rollback plan within the first business day.