This repository is a collection of Android quickstart samples demonstrating various Firebase products. Each sample is a standalone Android application showcasing integration with Firebase services such as Authentication, Realtime Database, Firestore, Cloud Storage, Cloud Functions, Analytics, and more. The samples are provided in both Java and Kotlin, often with parallel implementations, and follow modern Android architecture patterns including ViewModels, Navigation Component, and Jetpack Compose in newer samples. The repository includes shared internal modules for common UI components (chooserx) and custom lint rules (lintchecks) to maintain code quality across samples. The primary purpose is to serve as educational resources for developers learning to integrate Firebase into Android applications.

FlutterFire is a large monorepo of Flutter plugins that expose Firebase services to Flutter/Dart applications. It is not an end-user application but a client-side SDK layer: each Firebase product (Auth, Firestore, Storage, Functions, Messaging, Crashlytics, Remote Config, Analytics, App Check, AI, and more) is implemented as a separately published Flutter plugin with a shared Dart API, an abstract platform interface, and native implementations for Android, iOS, macOS, Web, and Windows. The architecture relies on Pigeon-generated message channels for typed Dart-to-native communication, custom codecs for Firebase-specific types, and event channels for real-time streams such as auth state, Firestore snapshots, and storage task progress. The primary entry point is Firebase.initializeApp() via firebase_core, after which each plugin's host API methods are invoked from Dart and dispatched to the native Firebase SDKs. The repository includes extensive example apps, unit tests, and GitHub Actions CI workflows with emulator-based integration tests across platforms.

FirebaseUI Web is a comprehensive authentication UI library for Firebase Auth, providing pre‑built, customizable screens, forms, and OAuth buttons across React, Angular, and Shadcn/UI frameworks. It follows a monorepo architecture with a framework‑agnostic core package (`@firebase-oss/ui-core`) that manages all authentication logic, state (via nanostores), and a composable behavior system for features like anonymous upgrade, legacy account recovery, reCAPTCHA, and One Tap. Framework‑specific packages (`react`, `angular`, `shadcn`) consume the core and render framework‑native components with consistent styling and i18n support. The library ships over 40 locale files, a translation system with fallback chains, and Zod‑based form validation that is reactive to locale changes. It supports the full set of Firebase Auth flows: email/password, email link (magic link), phone/SMS, OAuth providers (Google, Apple, Facebook, GitHub, Microsoft, Twitter, Yahoo, LINE, Snapchat), and multi‑factor authentication (SMS and TOTP enrollment/assertion). A custom auth server example demonstrates Snapchat OIDC integration. E2E tests with Playwright cover the major flows against the Firebase Auth emulator. Notable design decisions include a behavior plugin architecture that decouples optional features from core auth logic, a Shadcn component registry for user‑initiated installation (similar to shadcn/ui), and CSS variable theming to enable dark and brutalist themes. While the codebase is professionally structured and well‑tested, it carries some drift risks due to cross‑framework duplication of screens and forms, an unresolved AngularFire version gap (Angular 22 vs AngularFire 20), and several skipped integration tests that reduce confidence in end‑to‑end flows.

FirebaseUI-Android is an open-source library providing pre-built UI components for Firebase Authentication, Realtime Database, Cloud Firestore, and Cloud Storage. It is a multi-module Android library published on Maven Central. The primary module, `firebase-ui-auth`, has been rewritten in Jetpack Compose with Material 3, offering a high-level composable (`FirebaseAuthScreen`) and a Kotlin DSL for configuration. It supports 12+ identity providers (Google, Facebook, Email, Phone, Apple, etc.), multi-factor authentication (SMS/TOTP), credential linking, anonymous upgrade, and email link sign-in. The `firebase-ui-database` and `firebase-ui-firestore` modules provide RecyclerView adapters with paging support (AndroidX Paging 3) for displaying Firebase data. The `firebase-ui-storage` module integrates with Glide for loading images from Firebase Storage. A demo app and end-to-end tests against the Firebase Auth Emulator are included. Architecturally, the library is split into separate Gradle modules: `auth`, `database`, `firestore`, `storage`, `common`, and `lint`. The auth module uses Kotlin coroutines, StateFlow, and a sealed class state machine (`AuthState`) to manage authentication flows. The database/firestore modules are older Java-based implementations using lifecycle-aware adapters and observable arrays. The library maintains a version catalog (libs.versions.toml) with modern dependencies (Kotlin 2.4.10, AGP 9.3.0, Compose BOM 2026.06.01). Key entry points include `FirebaseAuthScreen` (Compose), `FirebaseAuthUI` (singleton for sign-out/delete/auth state), `AuthFlowController` (Activity-based alternative), `FirebaseRecyclerAdapter`/`FirestoreRecyclerAdapter`, and `FirebaseImageLoader` (Glide integration). The primary data flows involve Firebase SDKs for authentication, database listeners, and image loading. The library is designed to be embedded in host Android apps, handling complex auth flows with minimal developer effort. The codebase demonstrates strong craftsmanship in the auth module’s state machine and Compose UI, but shows signs of technical drift due to mixed UI generations (legacy XML layouts alongside new Compose), some deprecated API usage (e.g., `fetchSignInMethodsForEmail`, `startActivityForResult`), and incomplete localizations. The database/firestore modules are mature but use older patterns. Overall, the library is well-structured and actively maintained, with a beta version (10.0.0-beta04) indicating ongoing development.

firebase-tools is the official Firebase command-line interface. In production, it authenticates users against Google, resolves Firebase projects, and orchestrates deployments across functions, hosting, Firestore, Realtime Database, Storage, Extensions, App Hosting, Data Connect, Remote Config, and other services through a prepare→deploy→release pipeline. It also includes a full local emulator suite for Auth, Functions, Firestore, Storage, Database, Pub/Sub, Data Connect, Eventarc, and related services, plus framework integrations for Angular, Next.js, Nuxt, SvelteKit, Flutter, and other web stacks. The core shape is a TypeScript/Node CLI built from Command objects with ``before`` hooks for auth, permissions, and API enablement, backed by shared utilities for errors, prompts, HTTP clients, throttling, and operation polling. The repository has grown well beyond a simple CLI: ``src/mcp`` implements a Model Context Protocol server exposing Firebase operations to AI agents, and ``firebase-vscode`` is a complete VS Code extension with React webviews, Data Connect tooling, emulator controls, and its own test infrastructure. This makes the repo a multi-surface application rather than a data or research project. Craftsmanship is generally strong, with consistent cross-cutting patterns and extensive unit and integration tests. The main liabilities are feature sprawl, duplication between CLI commands and MCP tools, experimental feature flags, hardcoded runtime deprecation dates, and dependency-heavy integrations that will require ongoing maintenance as Firebase and Google Cloud APIs evolve.

Friendly Eats is an Android restaurant recommendation app that uses Firebase Firestore for real-time data synchronization and Firebase Authentication for user sign-in. The app features a main screen with a filterable and sortable list of restaurants, a detail view for individual restaurants, and the ability to add ratings. The architecture follows Android Jetpack guidelines with a single activity, multiple fragments, ViewModel for UI state, and the Navigation component for fragment transactions. Firestore queries are used to fetch and listen to restaurant data, with transactions ensuring data consistency when adding ratings.

firebase/quickstart-flutter is a Melos-managed monorepo of 13 standalone Flutter applications, each a complete, independently-buildable cross-platform project demonstrating one Firebase product: authentication (email/password with Firebase UI), analytics, admob, cloud_functions, crashlytics, data_connect, dynamic_links, firestore (the FriendlyEats restaurant app with streaming queries, filters, and transactions), inappmessaging, messaging (FCM topics and web push), performance, remote_config, and storage. Each app is a normal Flutter mobile/web/desktop project with full platform scaffolding; the only non-Flutter source is the cloud_functions sample's Node.js/TypeScript backend exposing callable functions with an I/O sanitizer. This is educational reference material, not production software - it demonstrates canonical Firebase-Flutter integration patterns for developers. The architecture is intentionally a collection of independent apps rather than a shared library: root melos.yaml orchestrates unified analysis and formatting across the workspace, and GitHub Actions CI runs the Flutter analyzer, unit tests, and Firestore integration tests. Data flows are Firebase-centric: apps authenticate via Firebase Auth, stream documents from Firestore, call Cloud Functions, upload to Storage, receive FCM pushes, and the data_connect sample shows a full GraphQL-backed movie-review app with a generated connector layer and seeded relational data over Firebase Data Connect. Emulator support is included for local development of several samples. Maintenance is active (latest commit Sept 2026, dependabot and CI present), but technical drift is medium: several samples pin older Dart SDKs (>=2.16/2.18), Gradle versions range from 6.7 to 8.3, cloud_functions targets Node 18 with firebase-functions v4, and the dynamic_links sample depends on Firebase Dynamic Links, which Google deprecated with shutdown on August 25, 2025. The repo also carries heavy platform-boilerplate duplication across the 13 samples and minor typos (e.g., 'Proflie Screen', 'sanatizeInput'). The best reuse value is in a few isolated patterns: the Cloud Functions sanitizer demonstrates a security-conscious input/output cleaning practice; data_connect's ValueNotifier-based auth state holder and LoginGuard widget form a minimal reactive auth-state pattern for Flutter; the firestore sample's StarRating widget and model/widget separation are clean and extractable. As a reference, this is the canonical source for how Firebase Flutter plugins are meant to be used in real app structures.