Skip to content

[PWA-75] Add PWA Wrapper documentation and capabilities overview#10931

Open
YogendraShelke wants to merge 7 commits intomendix:developmentfrom
YogendraShelke:development
Open

[PWA-75] Add PWA Wrapper documentation and capabilities overview#10931
YogendraShelke wants to merge 7 commits intomendix:developmentfrom
YogendraShelke:development

Conversation

@YogendraShelke
Copy link
Copy Markdown
Contributor

No description provided.

@YogendraShelke YogendraShelke changed the title Add PWA Wrapper documentation and capabilities overview [PWA-75] Add PWA Wrapper documentation and capabilities overview Mar 26, 2026
@ConnorLand ConnorLand self-assigned this Mar 26, 2026
@ConnorLand
Copy link
Copy Markdown
Collaborator

Are these docs tied to a release (SP or otherwise) or can they be merged whenever @YogendraShelke ?

@YogendraShelke
Copy link
Copy Markdown
Contributor Author

YogendraShelke commented Mar 26, 2026

Are these docs tied to a release (SP or otherwise) or can they be merged whenever @YogendraShelke ?

PWA Wrapper will be announced with the 11.9 release, but it is also supported on 10.24. It makes sense to publish these docs only after the PWA Wrapper marketplace module is released. I will confirm the timing once that release is completed.

@ConnorLand
Copy link
Copy Markdown
Collaborator

Ok, thank you @YogendraShelke, I'll wait to merge until you confirm the module release date. Cheers.

@YogendraShelke
Copy link
Copy Markdown
Contributor Author

Hi @ConnorLand, the PWA Wrapper has been published on the Marketplace. You can proceed with publishing the documentation now.

@ConnorLand
Copy link
Copy Markdown
Collaborator

I didn't get to editing these this week, but it's the top of my list for editing/merging when I get back from PTO on April 13 @YogendraShelke . It's got prio.

Copy link
Copy Markdown
Contributor

@jdiehl jdiehl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great job on the documentation! Very clear!

Keep the following recommendations in mind:

* Use one stable signing configuration per app line if you plan to publish updates
* Back up the generated Android signing directory before moving to another machine
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add instructions where to find the Android keystore

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this not the place mentioned in the Manage Signing Configurations section, above?

Copy link
Copy Markdown
Collaborator

@MarkvanMents MarkvanMents left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am most of the way through the review.
I wonder whether this documentation should be in a non-versioned area such as Marketplace. It doesn't make sense to be saying that it can be used on 10.24 when the documentation is in the Mendix 11 documentation. We could just have a landing page here, but all the instructions in the Marketplace.

I also see that the Marketplace module is not platform supported. Should this be changed now, or only when it comes out of beta.

I'll complete the review tomorrow.

Comment on lines +63 to +69
## 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/)
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need these - we normally only add Read More sections if the sections aren't linked above - and we already have all these listed very clearly.

Comment on lines +136 to +141
## 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).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to duplicate what is already in the steps. I don't think it adds anything.


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).

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.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be in the Android section only as you can't package resources on an iOS.


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/).
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what you mean here. If there are things that need referencing then the links should be in the build guide. I don't think we need to mention it here.

Keep the following recommendations in mind:

* Use one stable signing configuration per app line if you plan to publish updates
* Back up the generated Android signing directory before moving to another machine
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this not the place mentioned in the Manage Signing Configurations section, above?

1. Open PWA Wrapper and select **Android**.
2. Go to the signing step.
3. Select **Create New Signature**.
4. Enter a unique signature name such as `test`, `qa`, or `production`.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The one in the image isn't any of these, it is "debug". I think the suggestions should match the image.

Copy link
Copy Markdown
Collaborator

@MarkvanMents MarkvanMents left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have now finished my review.
I have a few minor questions, but my main concern is the position of these documents in the navigation.
I'll open a chat on Slack to make the discussion easier.
Thanks for the big PR - apologies for the delay in dealing with it.


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

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We list capabilities but don't actually identify any which are not available for Android or iOS. I don't think we need to say this - and we can always expand the tbale in the permission mapping if we decide to support other operating systems.

* 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.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this something the user should be handling as described in Designing with Capabilities?


## Introduction

This page summarizes the main cross-cutting limitations of PWA Wrapper in the current beta release.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean by "cross-cutting"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants