Firebase Rebrand Migration Status

Last updated: 2026-04-12

Current State

• Firebase project ID: homblabs-a1e67
• Active brand-facing app identifiers:
  • Android package: com.membloclabs.membloc
  • iOS/macOS bundle ID: com.membloclabs.membloc
  • Flutter package: membloc_app

Registered Firebase Apps

• Android membloc-app
  • App ID: 1:854204240417:android:ba3b71af070c6e2e298960
  • Package: com.membloclabs.membloc
• iOS membloc-app
  • App ID: 1:854204240417:ios:5e1df51cbb34b5cb298960
  • Bundle ID: com.membloclabs.membloc
• Web membloc-app-web
  • App ID: 1:854204240417:web:62b5e3ec529ae386298960

What Was Updated Locally

• membloc-app Firebase configs now point at the new app registrations.
• membloc-developer-portal/.env.example now ships the current public Firebase web config.

Remaining Migration Boundary

The project ID itself remains homblabs-a1e67. Renaming or replacing that project is a separate infra migration because it affects Auth, Firestore, Storage, Functions, authorized domains, and any deployed secrets.

Next Steps For Full Project-ID Migration

1. Create the target Firebase/GCP project with the final Membloc project ID.
2. Recreate Auth providers, Storage rules, Firestore indexes, Functions env, and authorized domains.
3. Export and import Firestore/Auth/Storage data.
4. Re-register Android, iOS, macOS, and web apps in the new project.
5. Regenerate platform SDK configs and rotate any environment variables that reference old app IDs.