diff --git a/content/en/docs/refguide/mobile/distributing-mobile-apps/_index.md b/content/en/docs/refguide/mobile/distributing-mobile-apps/_index.md index c7b3570b374..9d82128e183 100644 --- a/content/en/docs/refguide/mobile/distributing-mobile-apps/_index.md +++ b/content/en/docs/refguide/mobile/distributing-mobile-apps/_index.md @@ -14,6 +14,9 @@ Guides in this section will help you build, test and distribute mobile apps. Whi * [Building Native Apps](/refguide/mobile/distributing-mobile-apps/building-native-apps/) – The first step to install a native app on a mobile device is to create an application package (IPA on iOS and APK on Android). * [Distributing Native Apps](/refguide/mobile/distributing-mobile-apps/distributing-native-apps/) – To install an application package, it must be signed and submitted to the appropriate app stores (AppStore on iOS or PlayStore on Android) or installed via a mobile device management (MDM) solution. +* [Distribute a Mendix Native App with Appcircle](/refguide/mobile/distributing-mobile-apps/distributing-with-appcircle/) – This guide describes how to use Appcircle's Testing Distribution module to share builds with testers. +* [PWA Wrapper](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/) – This cluster of documents describes how you can use PWA wrapper to package and distribute a progressive web app (PWA) as a native app, then distribute it. +* [Publish a Mendix Native App with Appcircle](/refguide/mobile/distributing-mobile-apps/publishing-with-appcircle/) – This guide describes how to use Appcircle's Publish module to submit your Mendix native app to the App Store or Google Play. * [Updating Native Apps](/refguide/mobile/distributing-mobile-apps/overtheair-updates/) – Native apps are normally updated by building and distributing the updated version. In some situations (mainly for smaller changes) these steps can be skipped with an over-the-air update. * [Debugging Native Apps](/refguide/mobile/distributing-mobile-apps/native-debug/) – Web applications can be debugged directly in the web browser. For native apps, this is also possible but requires a few extra steps to set up. * [Testing Native Apps](/refguide/mobile/distributing-mobile-apps/testing-mobile-apps/) – To test native apps, third-party software is required. This guide explains how to use Appium to test native apps. diff --git a/content/en/docs/refguide/mobile/pwa-wrapper/_index.md b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/_index.md similarity index 73% rename from content/en/docs/refguide/mobile/pwa-wrapper/_index.md rename to content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/_index.md index f3ec00871c7..dc825c17624 100644 --- a/content/en/docs/refguide/mobile/pwa-wrapper/_index.md +++ b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/_index.md @@ -1,9 +1,10 @@ --- title: "PWA Wrapper" -url: /refguide/mobile/pwa-wrapper/ -weight: 45 +url: /refguide/mobile/distributing-mobile-apps/pwa-wrapper/ +weight: 26 description: "Package Mendix PWAs as native Android and iOS apps and use wrapper capabilities." -cascade: +aliases: + - /refguide/mobile/pwa-wrapper/ --- ## Introduction @@ -24,11 +25,11 @@ In summary: This PWA Wrapper documentation section includes the following topics: * Overview: this page explains what PWA Wrapper is and when to use it -* Installation guide: [Install PWA Wrapper](/refguide/mobile/pwa-wrapper/install-pwa-wrapper/) -* Build guide: [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/) -* Signing reference: [Sign PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/) explains the signing step in the build flow -* Capabilities guide: [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/) -* Limitations: [PWA Wrapper Limitations](/refguide/mobile/pwa-wrapper/pwa-wrapper-limitations/) +* Installation guide: [Install PWA Wrapper](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper/) +* Build guide: [Build PWA Wrapper Apps](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/) +* Signing reference: [Sign PWA Wrapper Apps](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/) explains the signing step in the build flow +* Capabilities guide: [PWA Wrapper Capabilities](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/) +* Limitations: [PWA Wrapper Limitations](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-limitations/) ## Typical Use Cases @@ -56,12 +57,4 @@ Keep the following limitations in mind: * Platform support varies for individual capabilities, so not every capability behaves the same way on Android and iOS * Some integrations use standard Web APIs, which means behavior can vary between devices, operating system versions, and embedded browser engines -For build-specific constraints, see [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/). For capability-specific constraints, see [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/). - -## Read More - -* [Install PWA Wrapper](/refguide/mobile/pwa-wrapper/install-pwa-wrapper/) -* [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/) -* [Sign PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/) -* [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/) -* [PWA Wrapper Limitations](/refguide/mobile/pwa-wrapper/pwa-wrapper-limitations/) +For build-specific constraints, see [Build PWA Wrapper Apps](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/). For capability-specific constraints, see [PWA Wrapper Capabilities](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). \ No newline at end of file diff --git a/content/en/docs/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps.md b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps.md similarity index 80% rename from content/en/docs/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps.md rename to content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps.md index 9a12350269b..f3136d539cb 100644 --- a/content/en/docs/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps.md +++ b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps.md @@ -1,15 +1,17 @@ --- title: "Build PWA Wrapper Apps" -url: /refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/ +url: /refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/ weight: 20 description: "Build Android APKs and iOS packages with PWA Wrapper." +aliases: + - /refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/ --- ## Introduction Use PWA Wrapper to generate Android and iOS packages from a Mendix PWA. The builder collects your app resources, applies wrapper configuration, and produces platform-specific build artifacts such as APK and IPA files. -Before following this guide, make sure you have completed [Install PWA Wrapper](/refguide/mobile/pwa-wrapper/install-pwa-wrapper/). +Before following this guide, make sure you have completed [Install PWA Wrapper](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper/). ## Build an Android APK @@ -23,7 +25,7 @@ Install Android Studio only if you want to use Android emulators for testing. To generate an Android APK, do the following: -1. [Open the builder](/refguide/mobile/pwa-wrapper/install-pwa-wrapper/#openbuilder) and select **Android**. +1. [Open the builder](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper/#openbuilder) and select **Android**. 1. In the app information step, enter the app metadata: * Version number @@ -42,14 +44,14 @@ To generate an Android APK, do the following: {{< figure src="/attachments/refguide/mobile/pwa-wrapper/capabilities.png" alt="Capabilities step in the PWA Wrapper builder" max-width="500px" >}} -1. Review the available permissions and enable only the permissions related to the capabilities your app uses. For capability-to-permission guidance, see [Capability to Permission Mapping](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/#capability-to-permission-mapping). +1. Review the available permissions and enable only the permissions related to the capabilities your app uses. For capability-to-permission guidance, see [Capability to Permission Mapping](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/#capability-to-permission-mapping). {{< figure src="/attachments/refguide/mobile/pwa-wrapper/permissions.png" alt="Permissions step in the PWA Wrapper builder" max-width="500px" >}} 1. Go to the signing step and do one of the following: * Choose an existing Android signing configuration - * Create a new signing configuration if this is the first Android build for the app; for platform-specific details, see [Sign Android Apps on Windows and macOS](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos) + * Create a new signing configuration if this is the first Android build for the app; for platform-specific details, see [Sign Android Apps on Windows and macOS](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos) {{< figure src="/attachments/refguide/mobile/pwa-wrapper/signature.png" alt="Signing step in the PWA Wrapper builder" max-width="500px" >}} 1. Click **Build**. @@ -68,7 +70,7 @@ The signing step is part of the Android build flow. The selected signing configu * Unsigned packages are suitable only for limited testing scenarios such as emulators * Signed packages are required for device installation and normal distribution workflows -For platform-specific details about the signing step, see [Sign Android Apps on Windows and macOS](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos). +For platform-specific details about the signing step, see [Sign Android Apps on Windows and macOS](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos). ### Android Output{#androidoutput} @@ -100,7 +102,7 @@ iOS packaging for a final signed device build requires macOS. On Windows, you ca To generate a signed iOS package on macOS, do the following: -1. [Open the builder](/refguide/mobile/pwa-wrapper/install-pwa-wrapper/#openbuilder) and select **iOS**. +1. [Open the builder](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper/#openbuilder) and select **iOS**. 1. In the app information step, enter the app metadata: * Version number @@ -117,7 +119,7 @@ To generate a signed iOS package on macOS, do the following: {{< figure src="/attachments/refguide/mobile/pwa-wrapper/capabilities.png" alt="Capabilities step in the PWA Wrapper builder" max-width="500px" >}} -1. Review the available permissions and enable only the permissions related to the capabilities your app uses. For capability-to-permission guidance, see [Capability to Permission Mapping](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/#capability-to-permission-mapping). +1. Review the available permissions and enable only the permissions related to the capabilities your app uses. For capability-to-permission guidance, see [Capability to Permission Mapping](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/#capability-to-permission-mapping). {{< figure src="/attachments/refguide/mobile/pwa-wrapper/permissions.png" alt="Permissions step in the PWA Wrapper builder" max-width="500px" >}} 1. Click **Build**. @@ -135,7 +137,7 @@ On Windows, use the same steps 1 through 7 as in [Steps for iOS on macOS](#steps 1. Open the output folder and locate the portable signing ZIP. 1. Copy the portable signing ZIP to a Mac. -1. Complete the final signing step on macOS as described in [Complete Signing on macOS](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#complete-signing-on-macos) in *Sign PWA Wrapper Apps*. +1. Complete the final signing step on macOS as described in [Complete Signing on macOS](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#complete-signing-on-macos) in *Sign PWA Wrapper Apps*. ### iOS Notes @@ -145,13 +147,13 @@ Keep the following limitations in mind: * The builder installation step for iOS is available only on macOS hosts * Copying packaged web resources is currently not supported on iOS, so the wrapped app must load its frontend resources from the deployed Mendix runtime -For platform-specific details about the signing step inside this build flow, see [Sign iOS Apps on macOS](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos) in *Sign PWA Wrapper Apps* for macOS builds and [Prepare iOS Apps on Windows](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#prepare-ios-apps-on-windows) in *Sign PWA Wrapper Apps* for Windows builds. +For platform-specific details about the signing step inside this build flow, see [Sign iOS Apps on macOS](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos) in *Sign PWA Wrapper Apps* for macOS builds and [Prepare iOS Apps on Windows](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#prepare-ios-apps-on-windows) in *Sign PWA Wrapper Apps* for Windows builds. ## Choosing Permissions and Packaging Options When configuring the wrapper, only enable the permissions and capabilities that your app actually uses. This reduces unnecessary prompts for end users and makes app review easier. -For a practical mapping between capabilities and the permissions you typically need to configure, see [Capability to Permission Mapping](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/#capability-to-permission-mapping). +For a practical mapping between capabilities and the permissions you typically need to configure, see [Capability to Permission Mapping](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/#capability-to-permission-mapping). If the builder offers a choice to skip copying web resources, use that option carefully. Skipping resource copy makes packaging faster, but the wrapped app will fetch its frontend resources from the runtime instead of using packaged resources. @@ -189,7 +191,7 @@ Keep the following testing limitations in mind while validating a wrapped app: * Hardware-dependent capabilities often require a physical device for realistic testing * Barcode and QR scanning, camera capture, geolocation, and biometric authentication should be validated on physical devices * Features such as network information, file download, URL opening, printing, sharing, local notifications, and permission flows can be tested first on simulators and emulators, but final verification should still happen on real devices -* Web API-backed capabilities such as network information, Share API flows, geolocation, notifications, and permission handling require a secure context. For more information, see [Secure Context](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/#secure-context) +* Web API-backed capabilities such as network information, Share API flows, geolocation, notifications, and permission handling require a secure context. For more information, see [Secure Context](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/#secure-context) * iOS physical-device testing requires a signed IPA * Capability behavior can differ between test devices even within the same platform @@ -199,6 +201,6 @@ If your app depends on device hardware, validate the final packaged app on repre After building the wrapper app, continue with the appropriate distribution process for your target platform. -If you still need platform-specific details for the signing step in the build flow, see [Sign Android Apps on Windows and macOS](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos), [Sign iOS Apps on macOS](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos), or [Prepare iOS Apps on Windows](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#prepare-ios-apps-on-windows). +If you still need platform-specific details for the signing step in the build flow, see [Sign Android Apps on Windows and macOS](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos), [Sign iOS Apps on macOS](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos), or [Prepare iOS Apps on Windows](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#prepare-ios-apps-on-windows). -To understand which capabilities you can use from your Mendix app, see [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/). +To understand which capabilities you can use from your Mendix app, see [PWA Wrapper Capabilities](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). diff --git a/content/en/docs/refguide/mobile/pwa-wrapper/install-pwa-wrapper.md b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper.md similarity index 85% rename from content/en/docs/refguide/mobile/pwa-wrapper/install-pwa-wrapper.md rename to content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper.md index c4d12ade18b..f45bfe64c7b 100644 --- a/content/en/docs/refguide/mobile/pwa-wrapper/install-pwa-wrapper.md +++ b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper.md @@ -1,8 +1,10 @@ --- title: "Install PWA Wrapper" -url: /refguide/mobile/pwa-wrapper/install-pwa-wrapper/ +url: /refguide/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper/ weight: 10 description: "Install and enable PWA Wrapper in Mendix Studio Pro." +aliases: + - /refguide/mobile/pwa-wrapper/install-pwa-wrapper/ --- ## Introduction @@ -17,7 +19,7 @@ Before installing [PWA Wrapper](https://marketplace.mendix.com/link/component/25 * You are using Mendix Studio Pro 10.24 or later -Platform-specific build and testing requirements such as Xcode or Xcode Command Line Tools, optional Android emulators or iOS simulators, and Apple signing assets are described in [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/). +Platform-specific build and testing requirements such as Xcode or Xcode Command Line Tools, optional Android emulators or iOS simulators, and Apple signing assets are described in [Build PWA Wrapper Apps](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/). ## Install PWA Wrapper @@ -48,5 +50,5 @@ Only request the permissions your app actually uses. This keeps the generated wr ## Read More -* [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/) -* [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/) +* [Build PWA Wrapper Apps](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/) +* [PWA Wrapper Capabilities](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/) diff --git a/content/en/docs/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities.md b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities.md similarity index 96% rename from content/en/docs/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities.md rename to content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities.md index 5db257508e5..766c4a0c05f 100644 --- a/content/en/docs/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities.md +++ b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities.md @@ -1,8 +1,10 @@ --- title: "PWA Wrapper Capabilities" -url: /refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/ +url: /refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/ weight: 30 description: "Overview of the capabilities exposed by the bundled PWA Wrapper JavaScript actions." +aliases: + - /refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/ --- ## Introduction diff --git a/content/en/docs/refguide/mobile/pwa-wrapper/pwa-wrapper-limitations.md b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-limitations.md similarity index 76% rename from content/en/docs/refguide/mobile/pwa-wrapper/pwa-wrapper-limitations.md rename to content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-limitations.md index a62d28fd8c8..adc5cb6e7b9 100644 --- a/content/en/docs/refguide/mobile/pwa-wrapper/pwa-wrapper-limitations.md +++ b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-limitations.md @@ -1,15 +1,17 @@ --- title: "PWA Wrapper Limitations" -url: /refguide/mobile/pwa-wrapper/pwa-wrapper-limitations/ +url: /refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-limitations/ weight: 35 description: "Known limitations and platform constraints for PWA Wrapper." +aliases: + - /refguide/mobile/pwa-wrapper/pwa-wrapper-limitations/ --- ## Introduction This page summarizes the main limitations of PWA Wrapper. -Use this page together with [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/), [Sign PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/), and [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/). +Use this page together with [Build PWA Wrapper Apps](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/), [Sign PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/), and [PWA Wrapper Capabilities](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). ## Scope Limitations @@ -17,7 +19,7 @@ Keep the following product-level limitations in mind: * Capability coverage is limited to the integrations currently provided by the bundled PWA Wrapper JavaScript actions -For an overview of the supported capabilities, see [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/). +For an overview of the supported capabilities, see [PWA Wrapper Capabilities](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). ## Build and Installation Constraints @@ -28,7 +30,7 @@ Keep the following build and installation constraints in mind: * Real-device installation requires signed packages * If an incompatible or newer build of the app is already installed on a device, it may need to be uninstalled before your current build can be installed -For build-specific steps and host-platform behavior, see [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/). +For build-specific steps and host-platform behavior, see [Build PWA Wrapper Apps](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/). ## Capability Limitations @@ -38,7 +40,7 @@ Some capabilities have additional platform or runtime constraints: * Features that rely on standard Web APIs can behave differently depending on operating system version, embedded browser engine, and secure-context availability * Platform support is not identical across all capabilities, so business-critical behavior must be verified on the target devices -For capability-specific requirements such as physical-device testing, secure context, and permission mapping, see [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/). +For capability-specific requirements such as physical-device testing, secure context, and permission mapping, see [PWA Wrapper Capabilities](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). ## Signing Limitations diff --git a/content/en/docs/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps.md b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps.md similarity index 96% rename from content/en/docs/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps.md rename to content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps.md index 18c816dc263..c34c5154f9b 100644 --- a/content/en/docs/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps.md +++ b/content/en/docs/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps.md @@ -1,15 +1,17 @@ --- title: "Sign PWA Wrapper Apps" -url: /refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/ +url: /refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/ weight: 25 description: "Configure Android and iOS signing for PWA Wrapper on macOS and Windows." +aliases: + - /refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/ --- ## Introduction This page explains the signing step within the PWA Wrapper build flow. It covers Android signing on Windows and macOS, iOS signing on macOS, and the Windows-to-macOS handoff required for final iOS signing. -Use this page as a reference while completing [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/). +Use this page as a reference while completing [Build PWA Wrapper Apps](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/). ## Signing in the Build Flow @@ -98,7 +100,7 @@ Keep the following recommendations in mind: Final iOS signing is only supported on macOS. -### Before You Start +### Before You Start {#before-you-start} Before creating the iOS signing configuration, make sure you have the following: @@ -178,7 +180,7 @@ Before starting the Windows flow, obtain the following files from your Apple sig * The `.p12` passphrase * A matching `.mobileprovision` file -You can create these files yourself through the Apple Developer workflow, or receive them from the team that manages your Apple signing assets. For Apple-specific certificate, provisioning profile, and Keychain export steps, see the official Apple documentation linked in [Before You Start](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/). +You can create these files yourself through the Apple Developer workflow, or receive them from the team that manages your Apple signing assets. For Apple-specific certificate, provisioning profile, and Keychain export steps, see the official Apple documentation linked in the [Before You Start](#before-you-start) section above. If the Apple signing assets are created on a Mac by another team member, confirm that the delivered files are a usable `.p12` export and a matching provisioning profile. A `.cer` file alone is not sufficient for PWA Wrapper. diff --git a/content/en/docs/refguide10/mobile/distributing-mobile-apps/_index.md b/content/en/docs/refguide10/mobile/distributing-mobile-apps/_index.md index ff1fd2002fa..adcc4d58b4c 100644 --- a/content/en/docs/refguide10/mobile/distributing-mobile-apps/_index.md +++ b/content/en/docs/refguide10/mobile/distributing-mobile-apps/_index.md @@ -14,6 +14,7 @@ Guides in this section will help you build, test and distribute mobile apps. Whi * [Building Native Apps](/refguide10/mobile/distributing-mobile-apps/building-native-apps/) – The first step to install a native app on a mobile device is to create an application package (IPA on iOS and APK on Android). * [Distributing Native Apps](/refguide10/mobile/distributing-mobile-apps/distributing-native-apps/) – To install an application package, it must be signed and submitted to the appropriate app stores (AppStore on iOS or PlayStore on Android) or installed via a mobile device management (MDM) solution. +* [PWA Wrapper](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/) – Use this guide to package Mendix PWAs as native Android and iOS apps, and use wrapper capabilities. * [Updating Native Apps](/refguide10/mobile/distributing-mobile-apps/overtheair-updates/) – Native apps are normally updated by building and distributing the updated version. In some situations (mainly for smaller changes) these steps can be skipped with an over-the-air update. * [Debugging Native Apps](/refguide10/mobile/distributing-mobile-apps/native-debug/) – Web applications can be debugged directly in the web browser. For native apps, this is also possible but requires a few extra steps to set up. * [Testing Native Apps](/refguide10/mobile/distributing-mobile-apps/testing-mobile-apps/) – To test native apps, third-party software is required. This guide explains how to use Appium to test native apps. diff --git a/content/en/docs/refguide10/mobile/pwa-wrapper/_index.md b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/_index.md similarity index 67% rename from content/en/docs/refguide10/mobile/pwa-wrapper/_index.md rename to content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/_index.md index 9826b097ab9..edd0a6469ac 100644 --- a/content/en/docs/refguide10/mobile/pwa-wrapper/_index.md +++ b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/_index.md @@ -1,16 +1,10 @@ --- title: "PWA Wrapper" -url: /refguide10/mobile/pwa-wrapper/ -weight: 45 +url: /refguide10/mobile/distributing-mobile-apps/pwa-wrapper/ +weight: 21 description: "Package Mendix PWAs as native Android and iOS apps and use wrapper capabilities." -cascade: - beta: true --- -{{% alert color="info" %}} -This feature is currently in beta. For more information, refer to [Release Status](/releasenotes/release-status/). -{{% /alert %}} - ## Introduction PWA Wrapper lets you package a Mendix progressive web app (PWA) as a native mobile app for Android and iOS. This is useful when you want to keep a web-based application architecture while distributing the app through app stores, installing it on managed devices, or adding a small set of commonly used hardware capabilities. @@ -21,7 +15,7 @@ PWA Wrapper does not replace Mendix native mobile development. It is intended fo In summary: -* If you need a fully native user interface based on React Native or broader native-device integration, see [Native Mobile](/refguide/mobile/introduction-to-mobile-technologies/native-mobile/). +* If you need a fully native user interface based on React Native or broader native-device integration, see [Native Mobile](/refguide10/mobile/introduction-to-mobile-technologies/native-mobile/). * If you want to keep a PWA architecture and add native packaging together with common mobile capabilities, PWA Wrapper is the better fit. ## Documentation Overview @@ -29,11 +23,11 @@ In summary: This PWA Wrapper documentation section includes the following topics: * Overview: this page explains what PWA Wrapper is and when to use it -* Installation guide: [Install PWA Wrapper](/refguide/mobile/pwa-wrapper/install-pwa-wrapper/) -* Build guide: [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/) -* Signing reference: [Sign PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/) explains the signing step in the build flow -* Capabilities guide: [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/) -* Limitations: [PWA Wrapper Limitations](/refguide/mobile/pwa-wrapper/pwa-wrapper-limitations/) +* Installation guide: [Install PWA Wrapper](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper/) +* Build guide: [Build PWA Wrapper Apps](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/) +* Signing reference: [Sign PWA Wrapper Apps](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/) explains the signing step in the build flow +* Capabilities guide: [PWA Wrapper Capabilities](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/) +* Limitations: [PWA Wrapper Limitations](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-limitations/) ## Typical Use Cases @@ -61,12 +55,4 @@ Keep the following beta limitations in mind: * Platform support varies for individual capabilities, so not every capability behaves the same way on Android and iOS * Some integrations use standard Web APIs, which means behavior can vary between devices, operating system versions, and embedded browser engines -For build-specific constraints, see [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/). For capability-specific constraints, see [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/). - -## Read More - -* [Install PWA Wrapper](/refguide/mobile/pwa-wrapper/install-pwa-wrapper/) -* [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/) -* [Sign PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/) -* [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/) -* [PWA Wrapper Limitations](/refguide/mobile/pwa-wrapper/pwa-wrapper-limitations/) +For build-specific constraints, see [Build PWA Wrapper Apps](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/). For capability-specific constraints, see [PWA Wrapper Capabilities](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). \ No newline at end of file diff --git a/content/en/docs/refguide10/mobile/pwa-wrapper/build-pwa-wrapper-apps.md b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps.md similarity index 75% rename from content/en/docs/refguide10/mobile/pwa-wrapper/build-pwa-wrapper-apps.md rename to content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps.md index db9a4924fec..8c4176f2bb8 100644 --- a/content/en/docs/refguide10/mobile/pwa-wrapper/build-pwa-wrapper-apps.md +++ b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps.md @@ -1,19 +1,15 @@ --- title: "Build PWA Wrapper Apps" -url: /refguide10/mobile/pwa-wrapper/build-pwa-wrapper-apps/ +url: /refguide10/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/ weight: 20 description: "Build Android APKs and iOS packages with PWA Wrapper." --- -{{% alert color="info" %}} -This feature is currently in beta. For more information, refer to [Release Status](/releasenotes/release-status/). -{{% /alert %}} - ## Introduction Use PWA Wrapper to generate Android and iOS packages from a Mendix PWA. The builder collects your app resources, applies wrapper configuration, and produces platform-specific build artifacts such as APK and IPA files. -Before following this guide, make sure you have completed [Install PWA Wrapper](/refguide/mobile/pwa-wrapper/install-pwa-wrapper/). +Before following this guide, make sure you have completed [Install PWA Wrapper](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper/). ## Build an Android APK @@ -27,7 +23,7 @@ Install Android Studio only if you want to use Android emulators for testing. To generate an Android APK, do the following: -1. [Open the builder](/refguide/mobile/pwa-wrapper/install-pwa-wrapper/#openbuilder) and select **Android**. +1. [Open the builder](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper/#openbuilder) and select **Android**. 2. In the app information step, enter the app metadata: * app name @@ -40,14 +36,14 @@ To generate an Android APK, do the following: {{< figure src="/attachments/refguide/mobile/pwa-wrapper/app-information.png" alt="Android app information step in the PWA Wrapper builder" max-width="500px" >}} -3. Review the available permissions and enable only the permissions related to the capabilities your app uses. For capability-to-permission guidance, see [Capability to Permission Mapping](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/#capability-to-permission-mapping). +3. Review the available permissions and enable only the permissions related to the capabilities your app uses. For capability-to-permission guidance, see [Capability to Permission Mapping](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/#capability-to-permission-mapping). {{< figure src="/attachments/refguide/mobile/pwa-wrapper/permissions.png" alt="Permissions step in the PWA Wrapper builder" max-width="500px" >}} 4. Go to the signing step and do one of the following: * choose an existing Android signing configuration - * create a new signing configuration if this is the first Android build for the app; for platform-specific details, see [Sign Android Apps on Windows and macOS](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos) + * create a new signing configuration if this is the first Android build for the app; for platform-specific details, see [Sign Android Apps on Windows and macOS](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos) 5. Continue to the packaging step and click **Generate Package**. {{< figure src="/attachments/refguide/mobile/pwa-wrapper/package-android-app.png" alt="Packaging step for building an Android APK with PWA Wrapper" max-width="500px" >}} @@ -64,7 +60,7 @@ The signing step is part of the Android build flow. The selected signing configu * Unsigned packages are suitable only for limited testing scenarios such as emulators * Signed packages are required for device installation and normal distribution workflows -For platform-specific details about the signing step, see [Sign Android Apps on Windows and macOS](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos). +For platform-specific details about the signing step, see [Sign Android Apps on Windows and macOS](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos). ### Android Output{#androidoutput} @@ -96,7 +92,7 @@ iOS packaging for a final signed device build requires macOS. On Windows, you ca To generate a signed iOS package on macOS, do the following: -1. [Open the builder](/refguide/mobile/pwa-wrapper/install-pwa-wrapper/#openbuilder) and select **iOS**. +1. [Open the builder](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper/#openbuilder) and select **iOS**. 2. In the app information step, enter the app metadata: * app name @@ -108,11 +104,11 @@ To generate a signed iOS package on macOS, do the following: * supported devices * screen orientation -3. Review the available permissions and enable only the permissions related to the capabilities your app uses. For capability-to-permission guidance, see [Capability to Permission Mapping](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/#capability-to-permission-mapping). -4. Go to the signing step and create or select an iOS signing configuration. For platform-specific details, see [Sign iOS Apps on macOS](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos). +3. Review the available permissions and enable only the permissions related to the capabilities your app uses. For capability-to-permission guidance, see [Capability to Permission Mapping](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/#capability-to-permission-mapping). +4. Go to the signing step and create or select an iOS signing configuration. For platform-specific details, see [Sign iOS Apps on macOS](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos). 5. Continue to the packaging step and click **Generate Package**. - {{< figure src="/attachments/refguide/mobile/pwa-wrapper/package-ios-app.png" alt="Packaging step for building an iOS package with PWA Wrapper" max-width="500px" >}} + {{< figure src="/attachments/refguide10/mobile/pwa-wrapper/package-ios-app.png" alt="Packaging step for building an iOS package with PWA Wrapper" max-width="500px" >}} 6. Wait for the build to complete. 7. Open the output directory and retrieve the generated artifacts. @@ -128,7 +124,7 @@ On Windows, use the same steps 1 through 7 as in [Steps for iOS on macOS](#steps 1. Open the output folder and locate the portable signing ZIP. 2. Copy the portable signing ZIP to a Mac. -3. Complete the final signing step on macOS as described in [Complete Signing on macOS](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#complete-signing-on-macos) in *Sign PWA Wrapper Apps*. +3. Complete the final signing step on macOS as described in [Complete Signing on macOS](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#complete-signing-on-macos) in *Sign PWA Wrapper Apps*. ### iOS Notes @@ -138,13 +134,13 @@ Keep the following limitations in mind: * The builder installation step for iOS is available only on macOS hosts * Copying packaged web resources is currently not supported on iOS, so the wrapped app must load its frontend resources from the deployed Mendix runtime -For platform-specific details about the signing step inside this build flow, see [Sign iOS Apps on macOS](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos) in *Sign PWA Wrapper Apps* for macOS builds and [Prepare iOS Apps on Windows](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#prepare-ios-apps-on-windows) in *Sign PWA Wrapper Apps* for Windows builds. +For platform-specific details about the signing step inside this build flow, see [Sign iOS Apps on macOS](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos) in *Sign PWA Wrapper Apps* for macOS builds and [Prepare iOS Apps on Windows](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#prepare-ios-apps-on-windows) in *Sign PWA Wrapper Apps* for Windows builds. ## Choosing Permissions and Packaging Options When configuring the wrapper, only enable the permissions and capabilities that your app actually uses. This reduces unnecessary prompts for end users and makes app review easier. -For a practical mapping between capabilities and the permissions you typically need to configure, see [Capability to Permission Mapping](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/#capability-to-permission-mapping). +For a practical mapping between capabilities and the permissions you typically need to configure, see [Capability to Permission Mapping](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/#capability-to-permission-mapping). If the builder offers a choice to skip copying web resources, use that option carefully. Skipping resource copy makes packaging faster, but the wrapped app will fetch its frontend resources from the runtime instead of using packaged resources. @@ -159,7 +155,7 @@ For Android: 3. Click **Install to Device**. 4. Open the app from the device launcher after installation completes. - {{< figure src="/attachments/refguide/mobile/pwa-wrapper/run-on-android-emulator.png" alt="Install the generated Android app on an emulator from the PWA Wrapper builder" max-width="500px" >}} + {{< figure src="/attachments/refguide10/mobile/pwa-wrapper/run-on-android-emulator.png" alt="Install the generated Android app on an emulator from the PWA Wrapper builder" max-width="500px" >}} For iOS on macOS: @@ -171,7 +167,7 @@ For iOS on macOS: 4. Click **Install to Device**. 5. Launch the app from the device or simulator after installation completes. - {{< figure src="/attachments/refguide/mobile/pwa-wrapper/run-on-ios-simulator.png" alt="Install the generated iOS app on a simulator from the PWA Wrapper builder" max-width="500px" >}} + {{< figure src="/attachments/refguide10/mobile/pwa-wrapper/run-on-ios-simulator.png" alt="Install the generated iOS app on a simulator from the PWA Wrapper builder" max-width="500px" >}} If installation fails, check the builder error message first. Common causes are missing signing, incompatible provisioning, unavailable devices, or an already installed newer build. @@ -182,7 +178,7 @@ Keep the following testing limitations in mind while validating a wrapped app: * Hardware-dependent capabilities often require a physical device for realistic testing * Barcode and QR scanning, camera capture, geolocation, and biometric authentication should be validated on physical devices * Features such as network information, file download, URL opening, printing, sharing, local notifications, and permission flows can be tested first on simulators and emulators, but final verification should still happen on real devices -* Web API-backed capabilities such as network information, Share API flows, geolocation, notifications, and permission handling require a secure context. For more information, see [Secure Context](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/#secure-context) +* Web API-backed capabilities such as network information, Share API flows, geolocation, notifications, and permission handling require a secure context. For more information, see [Secure Context](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/#secure-context) * iOS physical-device testing requires a signed IPA * Capability behavior can differ between test devices even within the same platform @@ -192,6 +188,6 @@ If your app depends on device hardware, validate the final packaged app on repre After building the wrapper app, continue with the appropriate distribution process for your target platform. -If you still need platform-specific details for the signing step in the build flow, see [Sign Android Apps on Windows and macOS](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos), [Sign iOS Apps on macOS](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos), or [Prepare iOS Apps on Windows](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/#prepare-ios-apps-on-windows). +If you still need platform-specific details for the signing step in the build flow, see [Sign Android Apps on Windows and macOS](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos), [Sign iOS Apps on macOS](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos), or [Prepare iOS Apps on Windows](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#prepare-ios-apps-on-windows). -To understand which capabilities you can use from your Mendix app, see [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/). +To understand which capabilities you can use from your Mendix app, see [PWA Wrapper Capabilities](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). diff --git a/content/en/docs/refguide10/mobile/pwa-wrapper/install-pwa-wrapper.md b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper.md similarity index 85% rename from content/en/docs/refguide10/mobile/pwa-wrapper/install-pwa-wrapper.md rename to content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper.md index 00ba66d4fec..160478b0dee 100644 --- a/content/en/docs/refguide10/mobile/pwa-wrapper/install-pwa-wrapper.md +++ b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper.md @@ -1,14 +1,10 @@ --- title: "Install PWA Wrapper" -url: /refguide10/mobile/pwa-wrapper/install-pwa-wrapper/ +url: /refguide10/mobile/distributing-mobile-apps/pwa-wrapper/install-pwa-wrapper/ weight: 10 description: "Install and enable PWA Wrapper in Mendix Studio Pro." --- -{{% alert color="info" %}} -This feature is currently in beta. For more information, refer to [Release Status](/releasenotes/release-status/). -{{% /alert %}} - ## Introduction This page explains how to install and enable PWA Wrapper. After installation, you can open the builder and package your Mendix app as an Android or iOS app. @@ -25,7 +21,7 @@ Before installing [PWA Wrapper](https://marketplace.mendix.com/link/component/25 * You are using Mendix Studio Pro 10.24 or later -Platform-specific build and testing requirements such as Xcode or Xcode Command Line Tools, optional Android emulators or iOS simulators, and Apple signing assets are described in [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/). +Platform-specific build and testing requirements such as Xcode or Xcode Command Line Tools, optional Android emulators or iOS simulators, and Apple signing assets are described in [Build PWA Wrapper Apps](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/). ## Install PWA Wrapper @@ -56,5 +52,5 @@ Only request the permissions your app actually uses. This keeps the generated wr ## Read More -* [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/) -* [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/) +* [Build PWA Wrapper Apps](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/) +* [PWA Wrapper Capabilities](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/) diff --git a/content/en/docs/refguide10/mobile/pwa-wrapper/pwa-wrapper-capabilities.md b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities.md similarity index 93% rename from content/en/docs/refguide10/mobile/pwa-wrapper/pwa-wrapper-capabilities.md rename to content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities.md index cb329f400dd..5adfbb2166b 100644 --- a/content/en/docs/refguide10/mobile/pwa-wrapper/pwa-wrapper-capabilities.md +++ b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities.md @@ -1,14 +1,10 @@ --- title: "PWA Wrapper Capabilities" -url: /refguide10/mobile/pwa-wrapper/pwa-wrapper-capabilities/ +url: /refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/ weight: 30 description: "Overview of the capabilities exposed by the bundled PWA Wrapper JavaScript actions." --- -{{% alert color="info" %}} -This feature is currently in beta. For more information, refer to [Release Status](/releasenotes/release-status/). -{{% /alert %}} - ## Introduction PWA Wrapper includes bundled JavaScript actions that a Mendix PWA can call from nanoflows. These actions expose device features through a combination of wrapper-native bridges and supported Web APIs. @@ -74,4 +70,4 @@ When you build a Mendix app with PWA Wrapper capabilities, follow these guidelin * Verify native behavior on physical devices, not only simulators or emulators * Align the configured wrapper permissions with the JavaScript actions your app calls -For more general guidance on permissions in Mendix mobile apps, see [App Permissions](/refguide/mobile/using-mobile-capabilities/generic-permission-action/). +For more general guidance on permissions in Mendix mobile apps, see [App Permissions](/refguide10/mobile/using-mobile-capabilities/generic-permission-action/). diff --git a/content/en/docs/refguide10/mobile/pwa-wrapper/pwa-wrapper-limitations.md b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-limitations.md similarity index 72% rename from content/en/docs/refguide10/mobile/pwa-wrapper/pwa-wrapper-limitations.md rename to content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-limitations.md index 047c11ddbd2..5d22ed050ba 100644 --- a/content/en/docs/refguide10/mobile/pwa-wrapper/pwa-wrapper-limitations.md +++ b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-limitations.md @@ -1,19 +1,15 @@ --- title: "PWA Wrapper Limitations" -url: /refguide10/mobile/pwa-wrapper/pwa-wrapper-limitations/ +url: /refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-limitations/ weight: 35 description: "Known limitations and platform constraints for PWA Wrapper in the current beta release." --- -{{% alert color="info" %}} -This feature is currently in beta. For more information, refer to [Release Status](/releasenotes/release-status/). -{{% /alert %}} - ## Introduction This page summarizes the main limitations of PWA Wrapper in the current beta release. -Use this page together with [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/), [Sign PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/), and [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/). +Use this page together with [Build PWA Wrapper Apps](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/), [Sign PWA Wrapper Apps](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/), and [PWA Wrapper Capabilities](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). ## Beta Scope Limitations @@ -21,7 +17,7 @@ Keep the following product-level limitations in mind: * Capability coverage is limited to the integrations currently provided by the bundled PWA Wrapper JavaScript actions -For an overview of the supported capabilities, see [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/). +For an overview of the supported capabilities, see [PWA Wrapper Capabilities](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). ## Build and Installation Constraints @@ -32,7 +28,7 @@ Keep the following build and installation constraints in mind: * Real-device installation requires signed packages * If an incompatible or newer build of the app is already installed on a device, it may need to be uninstalled before your current build can be installed -For build-specific steps and host-platform behavior, see [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/). +For build-specific steps and host-platform behavior, see [Build PWA Wrapper Apps](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/). ## Capability Limitations @@ -42,7 +38,7 @@ Some capabilities have additional platform or runtime constraints: * Features that rely on standard Web APIs can behave differently depending on operating system version, embedded browser engine, and secure-context availability * Platform support is not identical across all capabilities, so business-critical behavior must be verified on the target devices -For capability-specific requirements such as physical-device testing, secure context, and permission mapping, see [PWA Wrapper Capabilities](/refguide/mobile/pwa-wrapper/pwa-wrapper-capabilities/). +For capability-specific requirements such as physical-device testing, secure context, and permission mapping, see [PWA Wrapper Capabilities](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/). ## Signing Limitations @@ -52,4 +48,4 @@ Keep the following signing-related constraints in mind: * Development and distribution signing assets are not interchangeable * A `.cer` file by itself is not enough for PWA Wrapper iOS signing; you need the exported `.p12` file and its passphrase -For the full signing workflow and asset requirements, see [Sign PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/). +For the full signing workflow and asset requirements, see [Sign PWA Wrapper Apps](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/). diff --git a/content/en/docs/refguide10/mobile/pwa-wrapper/sign-pwa-wrapper-apps.md b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps.md similarity index 93% rename from content/en/docs/refguide10/mobile/pwa-wrapper/sign-pwa-wrapper-apps.md rename to content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps.md index 271bb7e83a7..ad464cf1c8b 100644 --- a/content/en/docs/refguide10/mobile/pwa-wrapper/sign-pwa-wrapper-apps.md +++ b/content/en/docs/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps.md @@ -1,19 +1,15 @@ --- title: "Sign PWA Wrapper Apps" -url: /refguide10/mobile/pwa-wrapper/sign-pwa-wrapper-apps/ +url: /refguide10/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/ weight: 25 description: "Configure Android and iOS signing for PWA Wrapper on macOS and Windows." --- -{{% alert color="info" %}} -This feature is currently in beta. For more information, refer to [Release Status](/releasenotes/release-status/). -{{% /alert %}} - ## Introduction This page explains the signing step within the PWA Wrapper build flow. It covers Android signing on Windows and macOS, iOS signing on macOS, and the Windows-to-macOS handoff required for final iOS signing. -Use this page as a reference while completing [Build PWA Wrapper Apps](/refguide/mobile/pwa-wrapper/build-pwa-wrapper-apps/). +Use this page as a reference while completing [Build PWA Wrapper Apps](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/build-pwa-wrapper-apps/). ## Signing in the Build Flow @@ -77,7 +73,7 @@ To create an Android signing configuration, do the following: 4. Enter a unique signature name such as `test`, `qa`, or `production`. 5. Click **Create Signature** to save the signature. -{{< figure src="/attachments/refguide/mobile/pwa-wrapper/create-android-signing-config.png" alt="Create a new Android signing configuration in PWA Wrapper" max-width=500px >}} +{{< figure src="/attachments/refguide10/mobile/pwa-wrapper/create-android-signing-config.png" alt="Create a new Android signing configuration in PWA Wrapper" max-width=500px >}} PWA Wrapper then creates the local keystore and stores the signing metadata for reuse in later builds. @@ -102,7 +98,7 @@ Keep the following recommendations in mind: Final iOS signing is only supported on macOS. -### Before You Start +### Before You Start {#before-you-start} Before creating the iOS signing configuration, make sure you have the following: @@ -140,7 +136,7 @@ After you have the Apple signing files, do the following: 7. Enter the `.p12` passphrase. 8. Click **Create Signature** to save the signature. -{{< figure src="/attachments/refguide/mobile/pwa-wrapper/create-ios-signing-config.png" alt="Create a new iOS signing configuration in PWA Wrapper" max-width=500px >}} +{{< figure src="/attachments/refguide10/mobile/pwa-wrapper/create-ios-signing-config.png" alt="Create a new iOS signing configuration in PWA Wrapper" max-width=500px >}} PWA Wrapper stores the signing configuration for later iOS builds. @@ -182,7 +178,7 @@ Before starting the Windows flow, obtain the following files from your Apple sig * The `.p12` passphrase * A matching `.mobileprovision` file -You can create these files yourself through the Apple Developer workflow, or receive them from the team that manages your Apple signing assets. For Apple-specific certificate, provisioning profile, and Keychain export steps, see the official Apple documentation linked in [Before You Start](/refguide/mobile/pwa-wrapper/sign-pwa-wrapper-apps/). +You can create these files yourself through the Apple Developer workflow, or receive them from the team that manages your Apple signing assets. For Apple-specific certificate, provisioning profile, and Keychain export steps, see the official Apple documentation linked in the [Before You Start](#before-you-start) section above. If the Apple signing assets are created on a Mac by another team member, confirm that the delivered files are a usable `.p12` export and a matching provisioning profile. A `.cer` file alone is not sufficient for PWA Wrapper. diff --git a/content/en/docs/refguide10/mobile/introduction-to-mobile-technologies/_index.md b/content/en/docs/refguide10/mobile/introduction-to-mobile-technologies/_index.md index 65e899e87b7..9487ea46e4c 100644 --- a/content/en/docs/refguide10/mobile/introduction-to-mobile-technologies/_index.md +++ b/content/en/docs/refguide10/mobile/introduction-to-mobile-technologies/_index.md @@ -23,7 +23,7 @@ Progressive web apps have several advantages over regular web applications: Publishing PWAs is the same as publishing regular web applications with Mendix. Once the application is deployed, users can simply access the PWA by opening the application URL. Considering PWA and web apps are equally easy to publish, we recommend you use PWAs to take advantage of their additional capabilities. -If you are using Mendix version 10.24.0 or above and want to distribute a Mendix PWA through mobile app stores or package it in a native shell, see [PWA Wrapper](/refguide10/mobile/pwa-wrapper/). +If you are using Mendix version 10.24.0 or above and want to distribute a Mendix PWA through mobile app stores or package it in a native shell, see [PWA Wrapper](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/). For more information, see [Progressive Web App](/refguide10/mobile/introduction-to-mobile-technologies/progressive-web-app/). diff --git a/content/en/docs/releasenotes/studio-pro/10/10.24.md b/content/en/docs/releasenotes/studio-pro/10/10.24.md index 941cc69d0cb..82e5a5b0629 100644 --- a/content/en/docs/releasenotes/studio-pro/10/10.24.md +++ b/content/en/docs/releasenotes/studio-pro/10/10.24.md @@ -49,6 +49,7 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for - We added a confirmation dialog when enabling anonymous user access in App Security, warning that unrestricted anonymous roles may expose data unintentionally. - We now allow microflow and entity parameters to be optional for Java actions. - We improved cleanup of queued tasks that are owned by missing nodes. +- Progressive web app (PWA) wrappers are now in GA. This feature allows you to package a PWA as a native app, and is especially useful when you want to keep a web-based application architecture while distributing the app through app stores. For more information, see [PWA Wrapper](/refguide10/mobile/distributing-mobile-apps/pwa-wrapper/). ### Fixes