Update Android publishing index page (#1400)

* Tidied up article

* Handle file renames.

* Fix links.

* Remove redirect to check content builds.

* Edits.

* Re-add redirect.

.openpublishing.redirection.json

@@ -83,6 +83,10 @@
     {
       "source_path": "docs/whats-new/dotnet-docs-maui-2023-02-01.md",
       "redirect_url": "/dotnet/maui/whats-new"
+    },
+    {
+      "source_path": "docs/android/deployment/overview.md",
+      "redirect_url": "/dotnet/maui/android/deployment"
     }
   ]
 }

docs/TOC.yml

@@ -703,7 +703,7 @@
             - name: Android
               items:
                 - name: Overview
-                  href: android/deployment/overview.md
+                  href: android/deployment/index.md
                 - name: Publish with the .NET CLI
                   href: android/deployment/publish-cli.md
             - name: iOS

docs/android/deployment/index.md

@@ -1,55 +1,46 @@
 ---
 title: "Publish a .NET MAUI app for Android"
 description: "Learn how to package and publish an Android .NET MAUI app."
-ms.date: 10/07/2022
+ms.date: 04/05/2023
 ---
 
 # Publish a .NET MAUI app for Android
 
 > [!div class="op_single_selector"]
 >
-> - [Publish for Android](overview.md)
+> - [Publish for Android](index.md)
 > - [Publish for iOS](../../ios/deployment/index.md)
 > - [Publish for macOS](../../mac-catalyst/deployment/index.md)
 > - [Publish for Windows](../../windows/deployment/overview.md)
 
 The final step in the development of a .NET MAUI app is to publish it. Publishing is the process of creating a package that contains the app and is ready for users to install on their devices. Packaging and deployment involve two essential tasks:
 
-- **Preparing for publication**
+- **Preparing for deployment**. A release version of the app is created that can be deployed to Android devices.
+- **Distribution**. The release version of an app is made available through one or more of the various distribution channels.
 
-  A release version of the app is created that can be deployed to Android devices.
+The following diagram illustrates the steps involved with publishing a .NET MAUI Android app:
 
-- **Distribution**
+:::image type="content" source="media/build-and-deploy-steps.png" alt-text="Build and deploy flowchart for .NET MAUI Android apps.":::
 
-  The release version of an app is made available through one or more of the various distribution channels.
-
-The following diagram illustrates the steps involved with publishing a .NET MAUI app:
-
-:::image type="content" source="media/overview/build-and-deploy-steps.svg" alt-text="Build and deploy flowchart":::
-
-As can be seen by the diagram above, the preparation is the same regardless of the distribution method that is used. There are several ways that an Android app may be released to users:
+As can be seen in the diagram above, preparing for deployment is identical regardless of the distribution method that's used. There are several ways that an Android app can be released to users:
 
+- **Through a market** – There are multiple Android marketplaces that exist for distribution, with the most well known being [Google Play](https://play.google.com/).
 - **Via a website** – A .NET MAUI app can be made available for download on a website, from which users may then install the app by clicking on a link.
 - **Via a file share** – Similar to a website, as long as the app package is available to the user, they can side-load it on their device.
-- **Through a market** – There are several Android marketplaces that exist for distribution, such as  [Google Play](https://play.google.com/) or [Amazon App Store for Android](https://www.amazon.com/mobile-apps/b?ie=UTF8&node=2350149011).
 
 Using an established marketplace is the most common way to publish an app as it provides the broadest market reach and the greatest control over distribution. However, publishing an app through a marketplace requires extra effort.
 
-Multiple channels can distribute a .NET MAUI app simultaneously. For example, an app could be published on Google Play, the Amazon App Store for Android, and also be downloaded from a web server.
+Multiple channels can distribute a .NET MAUI app simultaneously. For example, an app could be published on Google Play, and also be downloaded from a web server.
 
 Making your app available for direct download is most useful for a controlled subset of users, such as an enterprise environment or an app that is only meant for a small or well-specified set of users. Server and email distribution are also simpler publishing models, requiring less preparation to publish an app, though apps may be blocked as an email attachment.
 
-The Amazon Mobile App Distribution Program enables mobile app developers to distribute and sell their applications on Amazon. Users can discover and shop for apps on their Android devices by using the Amazon App Store application.
-
-Google Play is arguably the most comprehensive and popular marketplace for Android applications. Google Play allows users to discover, download, rate, and pay for applications by clicking a single icon either on their device or on their computer. Google Play also provides tools to help in the analysis of sales and market trends and to control which devices and users may download an application.
+Google Play is the most comprehensive and popular marketplace for Android apps. Google Play allows users to discover, download, rate, and pay for apps by clicking a single icon either on their device or on their computer. Google Play also provides tools to help in the analysis of sales and market trends and to control which devices and users may download an app.
 
 > [!IMPORTANT]
-> Blazor Hybrid apps require a WebView on the host platform. For more information, see [Keep the Web View current in deployed Blazor Hybrid apps](/aspnet/core/blazor/hybrid/security/security-considerations#keep-the-web-view-current-in-deployed-apps).
+> When distributing a Blazor Hybrid app, the host platform must have a WebView. For more information, see [Keep the Web View current in deployed Blazor Hybrid apps](/aspnet/core/blazor/hybrid/security/security-considerations#keep-the-web-view-current-in-deployed-apps).
 
 ## See also
 
-This section links to articles that may help in publishing an app to an app store such as Google Play.
-
 <!--
 - [Build Process](~/android/deploy-test/building-apps/build-process.md)
 - [Linking](~/android/deploy-test/linker.md)
@@ -58,12 +49,5 @@ This section links to articles that may help in publishing an app to an app stor
 - [Application Signing](https://source.android.com/security/apksigning/)
 -->
 
-### Google Play app store
-
 - [Publishing on Google Play](https://developer.android.com/distribute/googleplay/publish/index.html)
 - [Google Application Licensing](https://developer.android.com/guide/google/play/licensing/index.html)
-
-### Amazon app store
-
-- [Mobile App Distribution Portal](https://developer.amazon.com/welcome.html)
-- [Amazon Mobile App Distribution FAQ](https://developer.amazon.com/help/faq.html)

docs/deployment/index.md

@@ -14,7 +14,7 @@ You can debug and test your apps on the Android emulator, which can be run in a
 
 While the Android emulator enables you to rapidly develop and test your apps, you'll also want to test your apps on a real Android device. To run on a device, you'll need to enable developer mode on the device and connect it to your development machine. For more information, see [Set up Android device for debugging](~/android/device/setup.md).
 
-When distributing a .NET MAUI app for Android, you generate an *apk* (Android Package) or an *aab* (Android App Bundle) file. The *apk* is used for installing your app to an Android device, and the *aab* is used to publish your app to an Android store. With just a few configuration changes to your project, your app can be packaged for distribution. For more information, see [Publish a .NET MAUI app for Android](~/android/deployment/overview.md).
+When distributing a .NET MAUI app for Android, you generate an *apk* (Android Package) or an *aab* (Android App Bundle) file. The *apk* is used for installing your app to an Android device, and the *aab* is used to publish your app to an Android store. With just a few configuration changes to your project, your app can be packaged for distribution. For more information, see [Publish a .NET MAUI app for Android](~/android/deployment/index.md).
 
 ## iOS
 

docs/index.yml

@@ -181,7 +181,7 @@ landingContent:
           - text: Project configuration
             url: deployment/visual-studio-properties.md
           - text: Publish Android apps
-            url: android/deployment/overview.md
+            url: android/deployment/index.md
           - text: Publish iOS apps
             url: ios/deployment/index.md
           - text: Publish Mac Catalyst apps

docs/ios/deployment/index.md

@@ -8,7 +8,7 @@ ms.date: 02/24/2023
 
 > [!div class="op_single_selector"]
 >
-> - [Publish for Android](../../android/deployment/overview.md)
+> - [Publish for Android](../../android/deployment/index.md)
 > - [Publish for iOS](index.md)
 > - [Publish for macOS](../../mac-catalyst/deployment/index.md)
 > - [Publish for Windows](../../windows/deployment/overview.md)

docs/mac-catalyst/deployment/index.md

@@ -8,7 +8,7 @@ ms.date: 03/23/2023
 
 > [!div class="op_single_selector"]
 >
-> - [Publish for Android](../../android/deployment/overview.md)
+> - [Publish for Android](../../android/deployment/index.md)
 > - [Publish for iOS](../../ios/deployment/index.md
 > - [Publish for macOS](index.md)
 > - [Publish for Windows](../../windows/deployment/overview.md)

docs/windows/deployment/overview.md

@@ -8,7 +8,7 @@ ms.date: 10/12/2022
 
 > [!div class="op_single_selector"]
 >
-> - [Publish for Android](../../android/deployment/overview.md)
+> - [Publish for Android](../../android/deployment/index.md)
 > - [Publish for iOS](../../ios/deployment/index.md)
 > - [Publish for macOS](../../mac-catalyst/deployment/index.md)
 > - [Publish for Windows](overview.md)