Console Tour

# ===== 1. Project creation =====
# console.firebase.google.com -> Add project
# - Name + project ID (the ID is permanent and shows in URLs)
# - Optional: Analytics (Google Analytics integration)
# Once created, you land on the Project Overview.

# ===== 2. Add an app =====
# Overview -> </> for Web (or iOS / Android)
# - Register the app (give it a nickname)
# - (Optional) Firebase Hosting
# - Copy the firebaseConfig snippet (NOT a secret — it identifies the project)

# ===== 3. Navigation map =====
# Build:
#   Authentication           sign-in providers, user management
#   App Check                attestation (block scraping bots / spam)
#   Firestore Database       documents + collections
#   Realtime Database        legacy JSON tree
#   Storage                  file storage
#   Hosting                  CDN for static + functions
#   Functions                serverless code
#   Machine Learning         classifiers / translation
#   Extensions               drop-in marketplace
# Release and monitor:
#   Crashlytics              crash reporting
#   Performance              network + frame perf
#   Analytics                events + conversions
#   App Distribution         beta builds
#   Test Lab                 device farm
# Engage:
#   Remote Config            feature flags + targeting
#   Messaging                push + in-app
#   A/B Testing
# Run -> Cloud Messaging / In-App Messaging

# ===== 4. Things to configure on day one =====
# - Project settings -> default GCP resource location (cannot change later for Firestore!)
# - Authentication -> Sign-in method -> enable providers
# - Firestore -> create database (production mode + locked rules; not test mode)
# - Storage -> create default bucket with locked rules
# - Hosting -> connect your custom domain (optional)
# - App Check -> turn on for prod APIs

# ===== 5. Locked Firestore rules (default) =====
rules_version = '2';
service cloud.firestore {
  match /databases/{db}/documents {
    match /{document=**} {
      allow read, write: if false;
    }
  }
}
# Then loosen per collection as you build features.

# ===== 6. Budget alerts (very important) =====
# In Google Cloud (linked project) -> Billing -> Budgets and alerts
# Set a monthly cap with email at 50/80/100%.
# Hot Firestore listeners can balloon spend silently.

# ===== 7. Team access =====
# Project settings -> Users and permissions
# Roles: Owner / Editor / Viewer / fine-grained custom
# Use 2FA on every account with access.

# ===== Patterns to internalise =====
# - Pick the default location carefully (Firestore is region-locked)
# - Locked rules by default; loosen per feature
# - Enable App Check before launch
# - Always set budget alerts before opening to traffic

# ===== Pitfalls =====
# - Leaving Firestore in 'test mode' (open rules) past day 1
# - No budget alerts -> a runaway listener costs hundreds in a weekend
# - Firebase Hosting + Functions cold starts > 1s without min instances
# - Sharing firebaseConfig as if it is a secret (it is not; security lives in rules)

// console.firebase.google.com
// Pick / create a project. Build → Auth, Firestore, Functions, Storage, Hosting.