Publishing
Native Apps
Package a Manifest project as a native app for app stores or direct download.
Overview
A Manifest progressive web app (PWA) can run as a native-feeling app on every modern operating system. On most platforms, users can install the PWA directly from their browser with no packaging required. For app store presence and other distribution channels, the PWA needs to be wrapped in a native bundle and submitted through each platform's store. This article covers those native packaging paths.
Standard PWA wrappers work with any Manifest project. The most common is PWABuilder, a free tool from Microsoft that takes your live URL and produces store-ready packages for iOS, Android, and Windows from one workflow.
Apps by OS
| Format | Packaging | App Store | Open Distribution |
|---|---|---|---|
| Web App | — | — | Yes |
| iOS & iPadOS | Xcode project | App Store ($99/yr) | — |
| macOS | Xcode + Mac Catalyst | Mac App Store ($99/yr) | Yes |
| Android | AAB / APK | Google Play ($25) | Yes |
| Windows | MSIX | Microsoft Store ($19+) | Yes |
| ChromeOS | Android TWA | Google Play (via Android) | — |
| Linux | Snap, Flatpak, AppImage | Snap Store, Flathub | Yes |
iOS & iPadOS
- Packaging: PWABuilder generates an Xcode project that wraps the PWA in a WebKit view.
- App Store: Sign and upload through App Store Connect on a Mac. Requires an Apple Developer account ($99/yr). Beta distribution goes through TestFlight.
- Open Distribution: Limited. As of iOS 17.4, EU users can install from alternative app marketplaces. Elsewhere, the App Store is the only path.
macOS
- Packaging: PWABuilder generates the same Xcode wrapper as iOS, compiled for macOS via Mac Catalyst.
- App Store: Mac App Store submissions go through App Store Connect alongside iOS, on the same $99/yr Apple Developer account.
- Open Distribution: Bundle as a notarized
.dmgor.pkgand distribute from your own site, or publish through Homebrew Cask.
Android
- Packaging: PWABuilder or Google's Bubblewrap CLI wraps the PWA as a Trusted Web Activity (TWA), producing an AAB or APK.
- App Store: Submit the AAB through the Google Play Console. Requires a one-time $25 developer registration.
- Open Distribution: Amazon Appstore, Samsung Galaxy Store, and Huawei AppGallery all accept APKs. Users can also sideload an APK directly from any web download once they enable "Install unknown apps" for that source.
Windows
- Packaging: PWABuilder produces an MSIX package.
- App Store: Submit the MSIX through Microsoft Partner Center. Requires a developer account (one-time $19 individual, $99 company).
- Open Distribution: Distribute the MSIX directly from your site, or wrap as a traditional
.exeinstaller.
ChromeOS
- Packaging: ChromeOS doesn't require its own native wrapper. To reach the Play Store, reuse the Android TWA package.
- App Store: Google Play runs on ChromeOS, so the same Android submission reaches Chromebooks.
- Open Distribution: None. Direct browser install (covered under Web Apps) is the only path outside the Play Store.
Linux
- Packaging: Use the distribution-specific tool: Snapcraft for Snaps, Flatpak for Flatpaks, or AppImage for portable bundles.
- App Store: Publish to the Snap Store, Flathub, or the Arch User Repository depending on your reach.
- Open Distribution: An AppImage runs on most distributions without installation, suitable for direct download from your own site.
Article does not exist
There is no documentation at this path.