// the find
firebase/quickstart-unity
Firebase Quickstart Samples for Unity
Official Firebase sample apps for Unity, covering Analytics, Auth, Crashlytics, Firestore, Realtime Database, FCM, Remote Config, Storage, and more. Each Firebase product gets its own self-contained Unity project with a UIHandler.cs driving a minimal test UI. Aimed at Unity developers who need a working starting point or want to verify their Firebase setup.
- Every sample is a standalone Unity project with its own ProjectSettings, so you can open any one of them without pulling in unrelated dependencies or scenes.
- Firestore sample stands out: it includes actual integration tests (QueryAndListenerTests, TransactionAndBatchTests, etc.) with an asmdef, which is more than the usual hello-world quickstart.
- Functions sample bundles the companion Cloud Functions code (index.js) inside the project, so you can deploy the backend and test both ends together without hunting for separate repos.
- Actively maintained by Google with recent pushes and covers newer additions like Firebase AI (Gemini integration), keeping pace with SDK releases.
- Each sample is a completely separate Unity project, meaning no package manifest (Packages/manifest.json) is committed—you have to manually import the Firebase Unity SDK into every single one via .unitypackage or UPM, which is tedious and not documented well in the per-sample READMEs.
- The root README is nearly empty: two sentences and links to external docs. There's no matrix of which Unity version each sample was last tested against, no quick troubleshooting section, and no mention of the GoogleService-Info.plist/google-services.json setup that trips up every first-time user.
- The UI across all samples is the same legacy IMGUI GuiSkin approach—functional on device but visually dated and not representative of how you'd actually build a real Unity game UI, making it harder to adapt the code to a real project.
- Dynamic Links sample is included but Firebase Dynamic Links was deprecated and shut down in 2025, yet there's no deprecation warning in the sample README, which will confuse anyone who stumbles on it.