Polishing.

olivegamestudio · olivegamestudio · commit f52ec0977ea5 · 2025-09-28T16:21:09.000+01:00
diff --git a/articles/tutorials/advanced/MobileDeployment/02_crossplatform/index.md b/articles/tutorials/advanced/MobileDeployment/02_crossplatform/index.md
@@ -15,7 +15,7 @@ In this chapter you will:
 - **For iOS Development:**
   - An App Store Developer Account
   - **Certificates** and **Provisioning Profiles** configured and installed.
-  - **Mac with Xcode 16 installed** - installed through the App Store.
+  - **Mac 15.x (Sequoia) with Xcode 16 installed** - installed through the App Store.
 - **For Android Development:**
   - Android SDK and tools installed - through the Visual Studio Installer or through Jetbrains Rider.
 
diff --git a/articles/tutorials/advanced/MobileDeployment/03_touch/index.md b/articles/tutorials/advanced/MobileDeployment/03_touch/index.md
@@ -14,6 +14,10 @@ This is done during initialization:
 ```csharp
 protected override void Initialize()
 {
+    TouchPanel.DisplayWidth = GraphicsDevice.PresentationParameters.BackBufferWidth;
+    
+    TouchPanel.DisplayHeight = GraphicsDevice.PresentationParameters.BackBufferHeight;
+
     TouchPanel.EnabledGestures = GestureType.Tap |
                                  GestureType.DoubleTap |
                                  GestureType.Hold |
diff --git a/articles/tutorials/advanced/MobileDeployment/04_publishing/index.md b/articles/tutorials/advanced/MobileDeployment/04_publishing/index.md
@@ -5,27 +5,22 @@ description: "Learn how to publish your MonoGame mobile application to both the
 
 # Starting Publishing 
 
->>> TODO <<<<
+Before publishing your game to an app store, you need to sign up to the Apple Developer Program or Google Play.
 
-## Prerequisites
+There is a fee for both of these stores to allow you to publish your game.
 
-Before publishing, ensure you have:
-- Completed development and testing of your cross-platform MonoGame app
-- **For iOS:** Active Apple Developer Program membership (an annual fee)
-- **For Android:** Google Play Developer account (a one-time fee)
-- App icons, screenshots, and store assets prepared
-- Final build configurations tested on physical devices
+As part of the publishing process, a **bundle identifier** is a unique string, that distinctly identifies a mobile game or app across iOS and Android ecosystems for deployment.
 
 ### Understanding the Bundle Identifier
 
 The **bundle identifier** is a unique string that identifies your app. It follows a reverse domain name notation, such as `com.companyname.gamename`.
 
 This identifier is used by Apple and Google to distinguish your app from all others on the stores and on devices.
 
-- It **must** be unique across all apps in the store.
+- It **must** be unique across all apps and games in the store.
 
-- The bundle identifier you set in your project must exactly match the one registered in the stores.
+- The bundle identifier you set in your game project must exactly match the one registered in the stores.
 
-- Changing the bundle identifier after publishing will create a new app entry, not update the existing app.
+- Changing the bundle identifier after publishing will create a new app entry, not update the existing app, so carefully choose it.
 
 **Tip:** Choose a bundle identifier that reflects your organization and app name, and keep it consistent across your project files and provisioning profiles.
diff --git a/articles/tutorials/advanced/MobileDeployment/05_publishing_android/index.md b/articles/tutorials/advanced/MobileDeployment/05_publishing_android/index.md
@@ -7,25 +7,17 @@ description: "Learn how to publish your MonoGame mobile application to the Googl
 
 This chapter covers the complete publishing process for both major mobile app stores. You will learn the requirements and workflows for getting your MonoGame app successfully published on Android platforms.
 
-## Prerequisites
-
-Before publishing, ensure you have:
-- Completed development and testing of your cross-platform MonoGame app
-- Google Play Developer account (a one-time fee)
-- App icons, screenshots, and store assets prepared
-- Final build configurations tested on physical devices
+# Google Play Store Publishing
 
----
+## Creating Your Developer Account
 
-# Google Play Store Publishing
+**Register at** [play.google.com/console](https://play.google.com/console)
 
 ## Pre-Publishing Preparation
 
-### Final Android Build Configuration
+Ensure your Android project is properly configured for Google Play submission.
 
-Ensure your Android project is properly configured for Google Play submission:
-
-#### Project Properties
+## Project Properties
 
 ```xml
 <SupportedOSPlatformVersion>23</SupportedOSPlatformVersion>
@@ -34,9 +26,9 @@ Ensure your Android project is properly configured for Google Play submission:
 <ApplicationDisplayVersion>1.0</ApplicationDisplayVersion>
 ```
 
-#### Activity Configuration
+## Activity Configuration
 
-Verify your main activity is properly configured:
+Verify your main activity is properly configured. Ensuring the orientation of your game - portrait or landscape.
 
 ```csharp
 [Activity(
@@ -51,39 +43,38 @@ Verify your main activity is properly configured:
 )]
 ```
 
-### Required Assets
+## Required Assets
 
-#### App Icons
+### App Icons
 
-Ensure you have app icons for all density buckets:
+You will need to create and ensure you have app icons for all density buckets. There are a few online offerings where you can create a single image and it produce the icons. For example, [App Icon Generator](https://www.applicon.com).
 
 - **mdpi:** 48x48 px
 - **hdpi:** 72x72 px  
 - **xhdpi:** 96x96 px
 - **xxhdpi:** 144x144 px
 - **xxxhdpi:** 192x192 px
 
-#### Feature Graphic
+### Feature Graphic
 
 - **Size:** 1024 x 500 px
 - **Format:** PNG or JPEG
 - **Purpose:** Featured in Google Play Store
 
-#### Screenshots
+### Screenshots
 
-Required for each supported device type:
+Required for each supported device type to promote your game and its features.
 
 - **Phone:** Minimum 320px, maximum 3840px
 - **7-inch Tablet:** Same requirements
 - **10-inch Tablet:** Same requirements
 - **Android TV:** 1920 x 1080 px
 - **Wear OS:** 384 x 384 px
 
-### Release Build Configuration
+## Signing Configuration
 
-#### Signing Configuration
+### Creating a Keystore
 
-#### Creating a Keystore
 ```bash
 # Generate new keystore (first time only)
 keytool -genkey -v -keystore your-app.keystore -alias your-key-alias -keyalg RSA -keysize 2048 -validity 10000
@@ -94,13 +85,7 @@ keytool -list -v -keystore your-app.keystore
 
 **Important:** Keep your keystore file secure and backed up. Lost keystores cannot be recovered and prevent app updates.
 
-## Google Play Console Setup
-
-### Creating Your Developer Account
-
-**Register at** [play.google.com/console](https://play.google.com/console)
-
-### Creating Your App
+## Creating Your Game at Google Play
 
 1. **Create App** in Google Play Console
    
diff --git a/articles/tutorials/advanced/MobileDeployment/06_publishing_ios/index.md b/articles/tutorials/advanced/MobileDeployment/06_publishing_ios/index.md
@@ -7,28 +7,21 @@ description: "Learn how to publish your MonoGame mobile application to both the
 
 This chapter covers the complete publishing process for both major mobile app stores. You will learn the requirements, workflow for getting your MonoGame app successfully published on iOS platforms.
 
-## Prerequisites
+# Apple Develoer Program
 
-Before publishing, ensure you have:
-
-- Completed development and testing of your cross-platform MonoGame app
-- Active Apple Developer Program membership (an annual fee)
-- App icons, screenshots, and store assets prepared
-- Final build configurations tested on physical devices
-
-## Final iOS Build Configuration
+## Pre-Publishing Preparation
 
 Ensure your iOS project is properly configured for App Store submission:
 
-### Project Properties
+## Project Properties
 
 ```xml
 <SupportedOSPlatformVersion>12.2</SupportedOSPlatformVersion>
 <BundleIdentifier>com.companyname.gamename</BundleIdentifier>
 <CFBundleIconName>AppIcon</CFBundleIconName>
 ```
 
-### Code Signing for Release
+## Code Signing for Release
 
 Two entitlements - one for debug and one for publication.
 
@@ -39,7 +32,7 @@ Two entitlements - one for debug and one for publication.
 </PropertyGroup>
 ```
 
-#### Production Entitlements
+## Production Entitlements
 
 Verify your `EntitlementsProduction.plist` has debugging disabled:
 
@@ -52,14 +45,14 @@ Verify your `EntitlementsProduction.plist` has debugging disabled:
 
 ### App Icons
 
-Ensure your `Assets.xcassets/AppIcon.appiconset` contains all required sizes:
+You will need to create and ensure you have app icons for all density buckets. There are a few online offerings where you can create a single image and it produce the icons. For example, [App Icon Generator](https://www.applicon.com).
+
+You can place all of your icons in the location `Assets.xcassets/AppIcon.appiconset`.
 
 - **iPhone**: 40x40, 60x60, 87x87, 120x120, 180x180
 - **iPad**: 40x40, 58x58, 80x80, 152x152, 167x167  
 - **App Store**: 1024x1024
 
-These icons can be generated using a tool such as [AppIcon](https://www.applicon.com).
-
 |Asset|Image|
 |-|-|
 |40x40|![40x40](images/icons/appicon20x20@2x.png)|
@@ -74,7 +67,7 @@ These icons can be generated using a tool such as [AppIcon](https://www.applicon
 |180x180|![180x180](images/icons/appicon60x60@3x.png)|
 |Artwork 1024x1024|![1024x1024](images/icons/appiconItunesArtwork.png)|
 
-#### Info.plist Configuration
+### Info.plist Configuration
 
 Verify essential properties are set:
 
@@ -134,9 +127,7 @@ Ensure your iOS project includes the asset compilation target:
 </Target>
 ```
 
-## App Store Connect Setup
-
-### Creating Your App
+## Creating Game at App Store Connect
 
 1. **Log into App Store Connect** at [appstoreconnect.apple.com](https://appstoreconnect.apple.com)
 2. **Create New App:**
@@ -146,25 +137,25 @@ Ensure your iOS project includes the asset compilation target:
    - Bundle ID: Must match your project's `BundleIdentifier`
    - SKU: Unique identifier for your records
 
-### App Information
+## App Information
 
-#### Required Information
+### Required Information
 
 - **App Name:** Display name in the App Store
 - **Subtitle:** Brief description
 - **Category:** Primary and secondary categories
 - **Content Rights:** Whether you own or have licensed all content
 
-#### App Store Listing
+### App Store Listing
 
 - **Description:** Detailed app description
 - **Keywords:** Search terms (comma-separated)
 - **Marketing URL:** Your app's website
 - **Privacy Policy URL:** Required for most apps
 
-### Screenshots and Media
+## Screenshots and Media
 
-#### Required Screenshots
+### Required Screenshots
 
 You need screenshots for each device type you support:
 
@@ -174,29 +165,25 @@ You need screenshots for each device type you support:
 - **iPad Pro (6th gen)**: 2048 x 2732 pixels
 - **iPad Pro (2nd gen)**: 2048 x 2732 pixels
 
-#### App Preview Videos (Optional)
+### App Preview Videos (Optional)
 
 - 30 seconds maximum
 - Same dimensions as screenshots
 - Shows actual app gameplay
 
-## Building and Uploading
-
-### Archive Build Process
+## Building and Uploading using Terminal
 
-#### Using Command Line
-
-The creation of an IPA file can be achieved on the terminal. Currently, Rider does **not** support this process.
+The creation of an IPA file can be achieved on the terminal. Currently, Rider does **not** support this part of the process.
 
 ```sh
 dotnet clean
 rm -rf bin/ obj/
 dotnet publish -c Release -f net8.0-ios -r ios-arm64 -p:ArchiveOnBuild=true
 ```
 
-### Upload Method
+## Upload Method
 
-#### Transporter
+### Transporter
 
 - Standalone upload tool from Apple
 
@@ -216,7 +203,7 @@ dotnet publish -c Release -f net8.0-ios -r ios-arm64 -p:ArchiveOnBuild=true
 
 - Requires pre-signed IPA file
 
-### Build Processing
+## Build Processing
 
 After upload:
 
@@ -243,52 +230,3 @@ After upload:
 | ![Figure 4-6: Assign Testers](images/ios/testflight-build-assign-testers.png) |
 | :----------------------------------------------------------------------------------------------------------------------------------------: |
 |                       **Figure 4-6: Assign Testers** |    
-
-## App Review Submission
-
-### Pre-Submission Checklist
-
-- [ ] All required screenshots uploaded
-- [ ] App description and metadata complete
-- [ ] Privacy policy URL provided (if required)
-- [ ] Content rating completed
-- [ ] Pricing and availability set
-- [ ] Build selected and tested
-- [ ] Export compliance information provided
-
-### Review Information
-
-#### App Review Contact Information
-
-- First Name, Last Name
-- Phone Number
-- Email Address
-
-#### Demo Account (If Required)
-
-If your app requires login:
-- Demo Username
-- Demo Password
-- Additional instructions for reviewers
-
-#### Notes for Review
-
-Additional information to help reviewers:
-- Special instructions
-- Feature explanations
-- Known limitations
-
-### Submission Process
-
-1. **Select Build:** Choose your uploaded build
-2. **Review Summary:** Check all information is correct
-3. **Submit for Review:** Click "Submit for Review"
-4. **Status Tracking:** Monitor in App Store Connect
-
-## Review Timeline and Common Issues
-
-### Typical Timeline
-
-- **Review Time:** 24-48 hours
-- **Processing:** Additional time for first-time developers
-- **Holiday Delays:** Longer during Apple holidays, so plan accordingly.
diff --git a/articles/tutorials/advanced/MobileDeployment/07_checklist/index.md b/articles/tutorials/advanced/MobileDeployment/07_checklist/index.md
diff --git a/articles/tutorials/advanced/MobileDeployment/08_conclusion/index.md b/articles/tutorials/advanced/MobileDeployment/08_conclusion/index.md
