Restore binding-specific docs notes

AdamEssenmacher · AdamEssenmacher · commit dd644e044605 · 2026-04-20T17:48:10.000-04:00
diff --git a/docs/Firebase/NuGet/ABTesting.md b/docs/Firebase/NuGet/ABTesting.md
@@ -33,11 +33,19 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.ABTesting
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-No product walkthrough is maintained here. Add only binding-specific caveats that are not covered by the native docs.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
+
+Most app code uses A/B Testing indirectly through Remote Config, In-App Messaging, or Performance Monitoring. Direct use still requires Firebase to be configured first.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/Analytics.md b/docs/Firebase/NuGet/Analytics.md
@@ -33,11 +33,17 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.Analytics
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-No product walkthrough is maintained here. Add only binding-specific caveats that are not covered by the native docs.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/AppCheck.md b/docs/Firebase/NuGet/AppCheck.md
@@ -33,11 +33,19 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.AppCheck
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-No product walkthrough is maintained here. Add only binding-specific caveats that are not covered by the native docs.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
+
+If you use a debug or custom provider factory, call `Firebase.AppCheck.AppCheck.SetAppCheckProviderFactory(...)` before `Firebase.Core.App.Configure()`.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/AppDistribution.md b/docs/Firebase/NuGet/AppDistribution.md
@@ -33,11 +33,19 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.AppDistribution
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-Binding-specific caveat: The native Firebase App Distribution Apple SDK can use beta native framework versions behind the aggregate Firebase package line. Keep the NuGet package line aligned with the rest of Firebase in the application.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
+
+The native Firebase App Distribution Apple SDK can use beta native framework versions behind the aggregate Firebase package line. Keep the NuGet package line aligned with the rest of Firebase in the application.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/Auth.md b/docs/Firebase/NuGet/Auth.md
@@ -33,11 +33,17 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.Auth
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-No product walkthrough is maintained here. Add only binding-specific caveats that are not covered by the native docs.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/CloudFirestore.md b/docs/Firebase/NuGet/CloudFirestore.md
@@ -33,11 +33,17 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.CloudFirestore
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-No product walkthrough is maintained here. Add only binding-specific caveats that are not covered by the native docs.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/CloudFunctions.md b/docs/Firebase/NuGet/CloudFunctions.md
@@ -33,11 +33,17 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.CloudFunctions
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-No product walkthrough is maintained here. Add only binding-specific caveats that are not covered by the native docs.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/CloudMessaging.md b/docs/Firebase/NuGet/CloudMessaging.md
@@ -33,11 +33,19 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.CloudMessaging
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-No product walkthrough is maintained here. Add only binding-specific caveats that are not covered by the native docs.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
+
+Follow the official Firebase and Apple documentation for APNs registration and notification permissions; this package only exposes the managed binding surface.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/Core.md b/docs/Firebase/NuGet/Core.md
@@ -33,11 +33,17 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.Core
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-Binding-specific caveat: Most Firebase feature packages require the application to configure Firebase according to the official Apple setup docs before calling feature APIs.
+Call `Firebase.Core.App.Configure()` once from application startup after bundling the app-specific Firebase configuration. This is the .NET binding for native `FirebaseApp.configure()`.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/Crashlytics.md b/docs/Firebase/NuGet/Crashlytics.md
@@ -33,11 +33,19 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.Crashlytics
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-Binding-specific caveat: Crashlytics is native crash reporting. It is not a complete managed .NET exception-reporting replacement.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
+
+Crashlytics is native crash reporting, not a complete managed .NET exception-reporting replacement. On .NET 8 iOS projects, the top-level README includes an `_ExportSymbolsExplicitly` workaround for missing symbol/export issues.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/Database.md b/docs/Firebase/NuGet/Database.md
@@ -33,11 +33,17 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.Database
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-No product walkthrough is maintained here. Add only binding-specific caveats that are not covered by the native docs.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/InAppMessaging.md b/docs/Firebase/NuGet/InAppMessaging.md
@@ -33,11 +33,19 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.InAppMessaging
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-Binding-specific caveat: The native Firebase In-App Messaging Apple SDK can use beta native framework versions behind the aggregate Firebase package line. Keep the NuGet package line aligned with the rest of Firebase in the application.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
+
+The native Firebase In-App Messaging Apple SDK can use beta native framework versions behind the aggregate Firebase package line. Keep the NuGet package line aligned with the rest of Firebase in the application.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/Installations.md b/docs/Firebase/NuGet/Installations.md
@@ -33,11 +33,19 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.Installations
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-No product walkthrough is maintained here. Add only binding-specific caveats that are not covered by the native docs.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
+
+Some package combinations work more reliably when `AdamE.Firebase.iOS.Installations` is referenced explicitly, even if it appears to be transitive.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/PerformanceMonitoring.md b/docs/Firebase/NuGet/PerformanceMonitoring.md
@@ -33,11 +33,17 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.PerformanceMonitoring
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-No product walkthrough is maintained here. Add only binding-specific caveats that are not covered by the native docs.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/RemoteConfig.md b/docs/Firebase/NuGet/RemoteConfig.md
@@ -33,11 +33,17 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.RemoteConfig
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-No product walkthrough is maintained here. Add only binding-specific caveats that are not covered by the native docs.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
 
 ## Version Alignment
 
diff --git a/docs/Firebase/NuGet/Storage.md b/docs/Firebase/NuGet/Storage.md
@@ -33,11 +33,17 @@ When multi-targeting, condition package references so they restore only for Appl
 </ItemGroup>
 ```
 
+## Installation
+
+```sh
+dotnet add package AdamE.Firebase.iOS.Storage
+```
+
 ## Binding Notes
 
 Use the official Firebase Apple docs for setup and usage. In .NET, call the equivalent APIs from the managed namespace listed above. Keep app-specific Firebase configuration, such as `GoogleService-Info.plist`, in the application project.
 
-No product walkthrough is maintained here. Add only binding-specific caveats that are not covered by the native docs.
+Most Firebase feature packages require `AdamE.Firebase.iOS.Core` and app startup should call `Firebase.Core.App.Configure()` before feature APIs are used. This is the .NET binding for native `FirebaseApp.configure()`.
 
 ## Version Alignment
 
diff --git a/docs/Google/Maps/Details.md b/docs/Google/Maps/Details.md
@@ -14,4 +14,8 @@ These packages are thin .NET bindings over native Google Apple SDKs. Use the off
 - Managed namespace: `Google.Maps`
 - Status note: This binding project is present in the repository and is part of the current Google package set described by the top-level README.
 
+## Binding Notes
+
+The native `GMSServices.provideAPIKey` setup maps to `Google.Maps.MapServices.ProvideApiKey(apiKey)` in this binding. The managed namespace is `Google.Maps`.
+
 Document only binding-specific caveats in this repository. Product usage guidance belongs in the official native docs.
diff --git a/docs/Google/Maps/GettingStarted.md b/docs/Google/Maps/GettingStarted.md
@@ -14,4 +14,8 @@ These packages are thin .NET bindings over native Google Apple SDKs. Use the off
 - Managed namespace: `Google.Maps`
 - Status note: This binding project is present in the repository and is part of the current Google package set described by the top-level README.
 
+## Binding Notes
+
+The native `GMSServices.provideAPIKey` setup maps to `Google.Maps.MapServices.ProvideApiKey(apiKey)` in this binding. The managed namespace is `Google.Maps`.
+
 Document only binding-specific caveats in this repository. Product usage guidance belongs in the official native docs.
diff --git a/docs/Google/Places/Details.md b/docs/Google/Places/Details.md
@@ -14,4 +14,8 @@ These packages are thin .NET bindings over native Google Apple SDKs. Use the off
 - Managed namespace: `Google.Places`
 - Status note: This binding project is present in the repository and is part of the current Google package set described by the top-level README.
 
+## Binding Notes
+
+The native `GMSPlacesClient.provideAPIKey` setup maps to `Google.Places.PlacesClient.ProvideApiKey(apiKey)` in this binding. The managed namespace is `Google.Places`.
+
 Document only binding-specific caveats in this repository. Product usage guidance belongs in the official native docs.
diff --git a/docs/Google/Places/GettingStarted.md b/docs/Google/Places/GettingStarted.md
@@ -14,4 +14,8 @@ These packages are thin .NET bindings over native Google Apple SDKs. Use the off
 - Managed namespace: `Google.Places`
 - Status note: This binding project is present in the repository and is part of the current Google package set described by the top-level README.
 
+## Binding Notes
+
+The native `GMSPlacesClient.provideAPIKey` setup maps to `Google.Places.PlacesClient.ProvideApiKey(apiKey)` in this binding. The managed namespace is `Google.Places`.
+
 Document only binding-specific caveats in this repository. Product usage guidance belongs in the official native docs.
diff --git a/docs/Google/SignIn/Details.md b/docs/Google/SignIn/Details.md
@@ -14,4 +14,8 @@ These packages are thin .NET bindings over native Google Apple SDKs. Use the off
 - Managed namespace: `Google.SignIn`
 - Status note: This binding project is present in the repository and is part of the current Google package set described by the top-level README.
 
+## Binding Notes
+
+Use `Google.SignIn.Configuration` for native `GIDConfiguration`, assign it to `SignIn.SharedInstance.Configuration`, and pass callback URLs to `SignIn.SharedInstance.HandleUrl(url)`. Sign-in entry points are exposed on `SignIn.SharedInstance`.
+
 Document only binding-specific caveats in this repository. Product usage guidance belongs in the official native docs.
diff --git a/docs/Google/SignIn/GettingStarted.md b/docs/Google/SignIn/GettingStarted.md
@@ -14,4 +14,8 @@ These packages are thin .NET bindings over native Google Apple SDKs. Use the off
 - Managed namespace: `Google.SignIn`
 - Status note: This binding project is present in the repository and is part of the current Google package set described by the top-level README.
 
+## Binding Notes
+
+Use `Google.SignIn.Configuration` for native `GIDConfiguration`, assign it to `SignIn.SharedInstance.Configuration`, and pass callback URLs to `SignIn.SharedInstance.HandleUrl(url)`. Sign-in entry points are exposed on `SignIn.SharedInstance`.
+
 Document only binding-specific caveats in this repository. Product usage guidance belongs in the official native docs.
diff --git a/docs/Google/TagManager/Details.md b/docs/Google/TagManager/Details.md
@@ -14,4 +14,8 @@ These packages are thin .NET bindings over native Google Apple SDKs. Use the off
 - Managed namespace: `Google.TagManager`
 - Status note: This binding project is present in the repository. Check the top-level README and package feed for current publication status before depending on it.
 
+## Binding Notes
+
+Tag Manager initialization is exposed as `Google.TagManager.TagManager.Configure()`. Firebase-backed Tag Manager usage also depends on Firebase app initialization through `Firebase.Core.App.Configure()`.
+
 Document only binding-specific caveats in this repository. Product usage guidance belongs in the official native docs.
diff --git a/docs/Google/TagManager/GettingStarted.md b/docs/Google/TagManager/GettingStarted.md
@@ -14,4 +14,8 @@ These packages are thin .NET bindings over native Google Apple SDKs. Use the off
 - Managed namespace: `Google.TagManager`
 - Status note: This binding project is present in the repository. Check the top-level README and package feed for current publication status before depending on it.
 
+## Binding Notes
+
+Tag Manager initialization is exposed as `Google.TagManager.TagManager.Configure()`. Firebase-backed Tag Manager usage also depends on Firebase app initialization through `Firebase.Core.App.Configure()`.
+
 Document only binding-specific caveats in this repository. Product usage guidance belongs in the official native docs.
