docs: update documentation to reference firebase instead of AppCenter

Author: Kevin Takla

APP_README.md

@@ -81,10 +81,10 @@ TODO: Fill the following table with your own pipelines.
 | Link | Code Entry Point | Goal | Triggers |
 |-|-|-|-|
 | [Name of Main Pipeline](link-to-pipeline)| [`.azure-pipelines.yml`](.azure-pipelines.yml)| Build validation during pull request.| Pull requests.
-| [Name of Main Pipeline](link-to-pipeline)| [`.azure-pipelines.yml`](.azure-pipelines.yml)| Build and deploy the application to AppCenter, TestFlight, and GooglePlay. | Changes on the `main` branch.<br/>Manual trigger.
+| [Name of Main Pipeline](link-to-pipeline)| [`.azure-pipelines.yml`](.azure-pipelines.yml)| Build and deploy the application to Firebase, TestFlight, and GooglePlay. | Changes on the `main` branch.<br/>Manual trigger.
 | [Name of API Integration Tests Pipeline](link-to-pipeline)| [`.azure-pipelines-api-integration-tests.yml`](.azure-pipelines.yml)| Run all tests, including APIs integration tests. | Daily cron job.<br/>Manual trigger.
 | [Name of Canary Merge Pipeline](link-to-pipeline)| [`build/canary-merge.yml`](.azure-pipelines.yml)| Creation of canary branches (`canary/build/*`). | Daily cron job.
-| [Name of Canary Pipeline](link-to-pipeline)| [`.azure-pipelines-canary.yml`](.azure-pipelines.yml)| Build and deploy canary versions of the app to AppCenter and TestFlight. | Upon creation of branches with the `canary/build/*` pattern.
+| [Name of Canary Pipeline](link-to-pipeline)| [`.azure-pipelines-canary.yml`](.azure-pipelines.yml)| Build and deploy canary versions of the app to Firebase and TestFlight. | Upon creation of branches with the `canary/build/*` pattern.
 
 
 ## Additional Information

CHANGELOG.md

@@ -5,6 +5,9 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
 
 Prefix your items with `(Template)` if the change is about the template and not the resulting application.
 
+## 4.0.x
+- Using Firebase app distribution instead of AppCenter for internal distribution.
+
 ## 3.5.X
 - Bump Uno packages to 5.2.121 to fix a crash on iOS.
 - Ensure NV.Template.Mobile nuget is only deployed from the main branch.

doc/AzurePipelines.md

@@ -18,7 +18,7 @@ These pipelines rely on a few variable groups and secrets in order to fully work
 
 At high level, the CI/CD pipelines do the following:
 - **Build** the app in **staging**.
-  - **Deploy** the staging app (to AppCenter and/or TestFlight and GooglePlay).
+  - **Deploy** the staging app (to Firebase and/or TestFlight and GooglePlay).
 - **Build** the app in **production**.
   - **Deploy** the production app (to TestFlight and GooglePlay).
 
@@ -68,8 +68,8 @@ This is where the exact build steps are defined. These vary depending on the pla
 
 The release stages are even more straigtforward than the build ones. One thing to note is that, for the same reason as it is done at the end of the build steps, a clean-up step is included in every stage.
 
-### AppCenter Release Stage ([stage-release-appcenter.yml](../build/stage-release-appcenter.yml))
-This stage is in charge of pushing the application to AppCenter. It's divided into 2 jobs, one for each platform.
+### Firebase Release Stage ([stage-release-firebase.yml](../build/stage-release-firebase.yml))
+This stage is in charge of pushing the application to Firebase. It's divided into 2 jobs, one for each platform.
 
 ### Apple AppStore Release Stage ([stage-release-appstore.yml](../build/stage-release-appstore.yml))
 This stage is in charge of pushing the iOS version to the Apple AppStore. Given that the build stage signs the application, this is as simple as using the proper task and pushing the **IPA** file. This should only be run for configurations that properly sign the application.