Introduction
Let's ensure we understand the foundational concepts before delving further into the subjects. Here is a brief introduction if you are unfamiliar with the Firebase project.
Projects on the Google Cloud Platform that employ Firebase services are known as Firebase projects. This implies:
☑️ Billing and project permissions are shared between consoles.
☑️ Project-specific identifiers, such as the Project ID, are shared between consoles.
☑️ The Google Cloud Platform, APIs, and Firebase consoles display the same projects.
☑️ A project can be deleted and removed from all consoles.
This article explains the details of Interacting with a Firebase Project, in which we will talk about the relationship between Firebase projects, apps, and products, Relationship between Firebase projects and Google Cloud, Interacting with a Firebase project and Firebase project identifiers.
Without further ado, let's get started.
Understand Firebase projects
💁 You can share users, data, and analytics across platforms (Android, iOS, and web) using projects, ensuring that your users receive the same experience regardless of their device. To manage all versions of your app using the Firebase console, every Firebase-using app is associated with a Firebase project.
Relationship between Firebase projects, apps, and products
The highest-level entity in Firebase is a project. You can register your Android, Apple, or web apps in a project. After registering your apps with Firebase products, Any number of Firebase products, including Analytics, Cloud Firestore, Performance Monitoring, and Remote Config, can be added using the Firebase SDKs.
📁 Understanding the hierarchy of Firebase projects
A Firebase project's fundamental hierarchy is shown in this figure.
Here are the key connections:
☑️ All of your apps and any resources and services made available for the project are contained within a Firebase project.
☑️ All of your apps and any resources and services made available for the project are contained within a Firebase project.
☑️ One or more Firebase Apps may be registered to a Firebase project (for example, both the iOS and Android versions of an app, or both the free and paid versions of an app).
☑️ The resources and services provisioned for the project are shared by and available to all Firebase Apps registered to the same Firebase project. Here are a few instances:
✅ The same backends, such as Firebase Hosting, Authentication, Realtime Database, Cloud Storage, Cloud Firestore , and Cloud Functions, are shared by all Firebase Apps registered to the same Firebase project.
✅ Each Firebase App is a separate data stream in the Google Analytics property that is linked to all Firebase Apps registered to the same Firebase project.
Relationship between Firebase projects and Google Cloud
When you start a new Firebase project, you start a Google Cloud project. You can start with a Google Cloud project and eventually add Firebase. A Google Cloud project is a digital container for data, code, configuration, and services.
📁 A Google Cloud project uses Firebase:
☑️ In addition to the Google Cloud Console and the Google APIs console, you can also interact with a project in the Firebase console.
☑️ Products and APIs from Google Cloud and Firebase are both usable in projects.
☑️ Firebase and Google Cloud share billing and permissions for a project.
☑️ Project specific identifiers (such as project numbers and IDs) are exchanged between Firebase and Google Cloud.
☑️ A project's deletion affects both Google Cloud and Firebase.
Setting up a Firebase project and registering apps
💁 Create a project for Firebase and register apps in the Firebase console. Making organisational choices and including Firebase-specific configuration data in your local projects are necessary when setting up a project and registering apps.
For production apps, you must have a precise development workflow, which typically entails working in several settings. For information on setting up Firebase projects and registering apps, as well as general best practises and security recommendations, check our guidance on developer workflows.
Interacting with a Firebase project
You can communicate directly with a Firebase project using various tools and interfaces in addition to the product SDKs.
Firebase console
The Firebase console provides the most comprehensive environment for managing Firebase products, project-level settings, and apps.
The Firebase products are listed on the console's left-side panel, arranged by high-level categories. You may access a project's settings by clicking settings at the top of the left-side panel. Integrations, access restrictions, and billing are just a few of a project's options.
In the centre of the console are buttons that start setup processes for registering different kinds of apps. The main portion of the console transforms into a dashboard that shows statistics for the items you use once you start utilising Firebase.
Note that a Firebase project is also a Google Cloud project; there may be times when using the Google Cloud Console instead of the Firebase console is necessary to complete a task or use a product.
Firebase CLI (a command line tool)
Additionally, Firebase provides the Firebase CLI for setting up and managing various Firebase services, including Firebase Hosting, Firebase Extensions, and Cloud Functions for Firebase.
You can use the global firebase command once you have installed the CLI. When you want to publish fresh iterations of Firebase-hosted material or adjustments to functions, you can link your local app directory to a Firebase project using the CLI.
Firebase Management REST API
A Firebase project can be managed programmatically using the Firebase Management REST API. You might, for instance, list the apps that have previously been registered (iOS+ | Android | web) or register an app programmatically with a project.
Firebase project identifiers
A Firebase project can be located using a variety of identifiers, such as the project name, project number, and project ID, in the Firebase backend and multiple developer interfaces.
📂 The project name
You give the project a name when you create it. This identity serves as the project's internal-only name in the Firebase console, the Firebase CLI, and the Google Cloud Console. The project name makes it easier for you to distinguish between many projects; it is not disclosed in any publicly accessible Firebase or Google Cloud product, service, or resource
In the Firebase console's Project settings, you can edit a project's name whenever possible. The top pane shows the name of the project.
📂 The project number
A project number is assigned to each Firebase project (and related Google Cloud projects). This is the project's globally recognised canonical identification, as assigned by Google. Use this identifier when setting up integrations or making API requests to Firebase, Google, or other third-party services.
📂 The project ID
A project ID exists for each Firebase project (and related Google Cloud projects). This project-wide, globally unique identification spans Google Cloud and Firebase. A project's unique ID is automatically assigned by Firebase when you create it, but you can change it during project setup.
Firebase config files and objects
The Firebase console provides a Firebase configuration object (web apps) or file (Apple/Android apps) that you add directly to your local app directory when you register an app with a Firebase project.
✔️ You must include a GoogleService-Info.plist configuration file for Apple apps.
✔️ You include a google-services.json configuration file for Android apps.
✔️ You include a Firebase configuration object for web apps.
An app is connected to a particular Firebase project and its resources through a Firebase config file or object (databases, storage buckets, etc.). In order for Firebase and Google services to interact with Firebase server APIs and link client data to the Firebase project and Firebase app, the configuration contains "Firebase options," which are parameters. The necessary, minimal "Firebase settings" are as follows:
- API key: A short, encrypted string known as an API key is used when using specific APIs that don't require access to private user data.
-
Project ID: An individual, user-defined identifier for the project throughout Google Cloud and Firebase. This identifier might show up in some Firebase resource names or URLs, but it should normally be regarded as a handy alias to refer to the project.
-
Application ID ("AppID"): A platform-specific identifier for the Firebase app that is used across all of Firebase
- Firebase Apple apps: GOOGLE_APP_ID
- Firebase Android apps: mobilesdk_app_id
- Firebase Web apps: appId
The values specific to each Firebase project, such as the API Key, project ID, Cloud Storage bucket name, and Realtime Database URL, are considered public. This includes the platform-specific ID for the app (such as the Apple bundle ID or Android package name). To protect your data and files in Realtime Database, Cloud Storage, and Cloud Firestore, use Firebase Security Rules.
Because most of the time, your users should create their Firebase projects and point their apps to their Firebase resources, we normally do not recommend including the app's Firebase configuration file or object in source control for open source projects.
34+ registered 
