Google's app development platform console for backend services

How to Record Firebase Console

Record Firebase Console without exposing user data and project IDs. Guide for setup tutorials, Firestore demos, and security rules debugging.

When you’d need to record Firebase Console

Firebase setup tutorials for beginners

Record the full Firebase setup — create project, add app, configure Firestore, set up Authentication. Firebase docs assume prior knowledge — video walkthroughs show every click.

Firestore data modeling demonstrations

Record how to structure Firestore collections and documents — create collections, add documents, set up subcollections. Show the data hierarchy visually in the console while explaining your schema decisions.

Security rules debugging

Record the Rules Playground (Firestore > Rules > Edit > Simulate) to test security rules. Show a read/write simulation, check if the rule allows or denies, adjust the rule. Security rules are the #1 Firebase pain point — visual debugging is essential.

Cloud Functions deployment and logging

Record Cloud Functions deployment from the console or CLI, then show the Functions logs. Trace a function execution from trigger to completion — request, processing, response.

Recommended settings

Resolution

1920x1080

Frame rate

30fps

Audio

Microphone only

Capture mode

Window Capture

Things to know

•Firebase Console shows project IDs in the URL and header — project IDs are permanent and globally unique, identifying your project
•Firestore and Realtime Database viewers show actual document data — user records, messages, orders
•Authentication tab shows user email addresses, UIDs, and sign-in methods
•The project settings page shows API keys, service account emails, and project configuration

Step-by-step

1
In Screenify Studio, select Window Capture and pick the Firebase Console window.
Use a demo Firebase project. Production projects expose user data in Authentication and Firestore.
2
Open Firebase Console. Check the project selector (top bar) — it shows all your Firebase projects by name. Project names like 'client-app-production' or 'startup-name-staging' reveal your project structure. Use a demo project for public tutorials.
3
Check the URL — it contains your project ID: console.firebase.google.com/project/YOUR-PROJECT-ID/. Project IDs are permanent and identify your project's API endpoints. Be aware of this when sharing recordings.
4
If showing Firestore data, use the Firestore emulator or create a test collection with dummy data. Real Firestore documents may contain user PII, payment records, or internal business data.
5
Navigate to the specific Firebase service (Authentication, Firestore, Functions, Hosting) before recording. Firebase has 15+ services — use the sidebar to jump directly.

Pro tips

Auto-zoom on Firestore documents. Firestore's document viewer shows field names, types, and values in a compact tree structure. When you click a document to inspect it, auto-zoom zooms in so viewers can read the field values: 'name: string → John Doe, email: string → john@example.com'.

Use a demo project with seed data. Create a fresh Firebase project with test data in Firestore (fake users, sample posts, mock orders). Never record on production — Authentication shows real user emails, Firestore shows real customer data, Analytics shows real usage metrics.

Show the Rules Playground for security rules. Don't just show the rules text — demonstrate them. Open Rules > Simulate, set up a read/write scenario, run the simulation, show allow/deny result. Then modify the rule and re-simulate. This interactive approach teaches security rules far better than reading the syntax.

Record the emulator for local development tutorials. Firebase Local Emulator Suite runs Firebase services locally. Recording the emulator UI (localhost:4000) shows the same console interface without any production data risk. Ideal for tutorials.

Common mistakes

Recording with the Authentication tab open on a production project. Authentication lists every user: email, UID, creation date, last sign-in, providers. Scrolling through this tab exposes your entire user base. Use a demo project with fake test users.

Showing the project ID without awareness. Firebase project IDs appear in the URL, the project settings, and every SDK initialization snippet. Combined with your project's API key (also visible in settings), someone can identify and potentially probe your Firebase project.

Demonstrating Firestore with real production data. You open a Firestore collection called 'users' and it shows real customer documents with names, emails, addresses, and payment info. Use the Firestore emulator or a separate demo project with seed data.

Not showing the security rules alongside Firestore data. You demonstrate creating and reading documents but never show the security rules that govern access. Viewers copy your tutorial, deploy with default open rules, and get hacked. Always show Firestore > Rules as part of any Firestore tutorial.