PWA Wrapper Capabilities

Last modified: April 10, 2026

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.

Support can vary by platform, operating system version, browser engine, and configured permissions. Always test the capabilities you depend on using the actual devices you plan to support.

In the current beta release, PWA Wrapper capabilities are documented for Android and iOS.

Supported Capabilities

Verify the final packaged app on representative physical devices before release.

Capability Description Physical device required Secure context required
Scan barcode and QR code Opens the camera to scan supported barcode and QR formats from a nanoflow. Yes No
Network information Reads the current connection state so the app can react to online or offline conditions. No Yes
File download using the Share API Hands a generated file to the system share flow so the user can save or forward it. No Yes
Open URL Opens an external or deep link from the wrapped app. No No
Print file documents Sends a supported file to the platform print flow. No No
Share Shares text, links, or files with other apps or system services. No Yes
Upload pictures from the camera or gallery Lets the user capture a photo or select an existing image for upload. Yes No
Upload videos from the camera or gallery Lets the user capture a video or select an existing video for upload. Yes No
Geolocation Retrieves the device location for map, tracking, or location-aware flows. Yes Yes
Local notification Schedules or shows notifications generated by the app on the device. No Yes
Permissions Checks or requests supported runtime permissions from the app flow. No Yes
Biometric authentication Checks biometric availability and prompts the user for biometric authentication. This depends on device hardware and biometric enrollment. Yes No

Secure Context Required

Some PWA Wrapper capabilities rely on standard Web APIs that are only available in a secure context.

A secure context typically means one of the following:

  • the app is loaded over HTTPS
  • the app is accessed from localhost during local development

If the wrapped app is loaded from an insecure HTTP origin, capabilities that depend on Web APIs such as geolocation, notifications, permission handling, network information, or Share API flows may not work as expected.

Capability to Permission Mapping

Use the following table as a practical guide when deciding which permissions to configure in the builder.

Capability Android builder permissions iOS builder permissions
Scan barcode and QR code Camera Camera Usage
Upload pictures from the camera or gallery Camera Camera Usage
Upload videos from the camera or gallery Camera, Record Audio Camera Usage, Microphone Usage
Geolocation Fine Location, Coarse Location Location - When In Use Usage
Local notification Notifications No explicit builder permission message required

When a capability relies on camera, location, or notifications, align the configured builder permissions with the JavaScript actions your app actually calls. For video capture flows, also verify whether the target platform requires microphone permission.

Designing with Capabilities

When you build a Mendix app with PWA Wrapper capabilities, follow these guidelines:

  • Request permissions only when they are needed in the user flow
  • Handle denied permissions or unsupported devices by providing clear fallback logic
  • 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.