You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: contributor-docs/how_firebase_works.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -10,24 +10,24 @@ One of the biggest strengths for Firebase clients is the ease of integration. In
10
10
*`Firebase Performance` automatically tracks app startup time, all network requests and screen performance
11
11
*`Crashlytics` automatically captures all application crashes, ANRs and non-fatals
12
12
13
-
The ability to initialize and start operating automatically is a core feature of Firebase that makes onboarding and adoption very simple. However with this advantage comes a great responsibility to keep the application snappy and not to slow down application startup for 3p developers as it can stand in the way of user adoption for the application.
13
+
This feature makes onboarding and adoption very simple. However, comes with the great responsibility of keeping the application snappy. We shouldn't slow down application startup for 3p developers as it can stand in the way of user adoption of their application.
14
14
15
15
### Automatic Inter-Product Discovery
16
16
17
-
In addition to initializing automatically, when present together in an application, Firebase products can detect each other’s presence and automatically provide additional functionality to the developer, e.g.:
17
+
When present together in an application, Firebase products can detect each other and automatically provide additional functionality to the developer, e.g.:
18
18
19
19
*`Firestore` automatically detects `Auth` and `AppCheck` to protect read/write access to the database
20
-
*`Crashlytics` integrates with `Analytics`, when it’s available, to provide additional insights into the application behavior and enables safe app rollouts
20
+
*`Crashlytics` integrates with `Analytics`, when available, to provide additional insights into the application behavior and enables safe app rollouts
21
21
22
22
## FirebaseApp at the Core of Firebase
23
23
24
-
Regardless of what Firebase SDKs are present in the app, the main initialization point of Firebase is `FirebaseApp` it acts as a container for all SDKs, manages their configuration, initialization and lifecycle.
24
+
Regardless of what Firebase SDKs are present in the app, the main initialization point of Firebase is `FirebaseApp`. It acts as a container for all SDKs, manages their configuration, initialization and lifecycle.
25
25
26
26
### Initialization
27
27
28
-
`FirebaseApp` gets initialized with the help of `FirebaseApp#initializeApp()`, this happens [automatically at app startup](https://firebase.blog/posts/2016/12/how-does-firebase-initialize-on-android) or manually by the developer.
28
+
`FirebaseApp` gets initialized with the help of `FirebaseApp#initializeApp()`. This happens [automatically at app startup](https://firebase.blog/posts/2016/12/how-does-firebase-initialize-on-android) or manually by the developer.
29
29
30
-
When that happens`FirebaseApp` discovers all Firebase SDKs present in the app, determines the dependency graph between products(for inter-product functionality) and initializes `eager` products that need to start immediately, e.g. `Crashlytics` and `FirebasePerformance`.
30
+
During initialization,`FirebaseApp` discovers all Firebase SDKs present in the app, determines the dependency graph between products(for inter-product functionality) and initializes `eager` products that need to start immediately, e.g. `Crashlytics` and `FirebasePerformance`.
0 commit comments