Certificate

# ===== Skills checklist =====
# After the Firebase track you should be able to:
# [x] Initialise an app with flutterfire/firebase-tools and pick the right products
# [x] Write Firestore security rules that pass unit tests
# [x] Enforce App Check on Auth + Firestore + Functions
# [x] Build a per-user data model with appropriate indexes
# [x] Deploy a Cloud Function (HTTP, Firestore trigger, scheduled)
# [x] Use Crashlytics to track crashes + non-fatals (with symbol upload)
# [x] Send push notifications via FCM (web + iOS + Android)
# [x] Implement phone / Google / Apple auth flows
# [x] Export Analytics to BigQuery for SQL analysis
# [x] Schedule backups of Firestore to GCS
# [x] Test against the emulator suite in CI
# [x] Implement Remote Config flags + AB tests
# [x] Cost-monitor + alert before runaway bills

# ===== Bookmark =====
# - https://firebase.google.com/docs           official docs
# - https://firebase.google.com/codelabs
# - https://firebase.blog
# - https://github.com/invertase                 third-party SDKs + tools
# - https://invertase.io/oss                     React Native Firebase

# ===== Portfolio project (8-16 hours) =====
# Build and ship a small public app:
# 1) Web + mobile clients (Flutter or React + RN)
# 2) Auth: anonymous OR Google sign-in
# 3) Firestore-backed feature (notes, lists, tasks)
# 4) Cloud Function trigger that runs on doc create (audit, notification)
# 5) Security rules with full unit-test coverage
# 6) App Check enforced
# 7) Crashlytics + Analytics + Remote Config flag for an experiment
# 8) Hosted at <name>.web.app via Firebase Hosting
# 9) Scheduled backup function exporting to GCS
# 10) README + a CONTRIBUTING that mentions emulator + rules tests

# Bonus:
# - Push notifications via FCM
# - BigQuery exported Analytics with a sample SQL query
# - Phone auth with App Check protection

# ===== What 'good' looks like =====
# - Rules tests pass in CI before deploy
# - App Check enforcement panels are GREEN
# - No 'allow read, write: if true' anywhere
# - Cloud Function deploy is idempotent (deploy multiple times safely)
# - Backups verified by restoring to a sandbox project
# - Cost ceiling alert wired up

# ===== Common mistakes to avoid =====
# - Skipping App Check; bots will burn quota
# - Anonymous writes without rate limit
# - Heavy DB reads from the client without pagination
# - Functions deployed without minInstances=1 on hot paths
# - Crashlytics missing symbols (dSYMs / mapping.txt)
# - Loading 10k docs into memory; paginate with cursors

# ===== Next steps =====
# - Identity Platform for fancier auth flows
# - Firebase App Distribution for beta testing
# - Firestore data bundles for fast cold-start
# - Server-side rendering via Cloud Run + Firebase Hosting

# ===== Self-test =====
# If you can:
# 1) Write rules that pass the emulator tests in 5 minutes
# 2) Diagnose 'reads spiked, bill jumped' via Firestore usage panel
# 3) Stand up an app from 0 to deployed in an afternoon
# you have completed the track. Ship the portfolio piece and call it done.

# ===== Track wrap-up =====
# Firebase is the right backend when speed-to-market matters more than control.
# Rules tests + App Check + a backup story are the three habits that turn it
# from 'fast prototyping' into 'I can ship this to real users'.

// /certificate/firebase