Publish to App Stores
Wrap your published PWA with PWA Builder to generate Android, iOS, and Windows packages. A guided in-builder flow is on the roadmap.
Proyecta builds web apps. To distribute through the App Store, Google Play, or Microsoft Store, you wrap your published app as a PWA and use a tool like PWA Builder to generate native packages.
Step 1: Make sure your app is a PWA
Section titled “Step 1: Make sure your app is a PWA”Before generating store packages, ask the AI to add PWA support:
Add PWA support to my app:- Web app manifest with name, short name, icons (192px and 512px), theme color- Service worker that caches the app shell for offline use- Install promptThen publish to your *.proyecta.live subdomain (or a custom domain).
Step 2: Generate store packages
Section titled “Step 2: Generate store packages”- Open pwabuilder.com
- Enter your published URL
- PWA Builder runs a manifest/service worker/security audit
- Click Package for Stores and pick a target:
- Android — generates an
.aab(Android App Bundle) for Google Play - iOS — generates an Xcode project you build and submit via Xcode + Transporter
- Windows — generates an
.msixfor the Microsoft Store
- Android — generates an
Step 3: Submit
Section titled “Step 3: Submit”Each store has its own developer console:
| Store | Developer fee | Notes |
|---|---|---|
| Google Play | $25 one-time | Generally permissive of PWA wrappers |
| Apple App Store | $99/year | Apple may reject apps that are just a webview without native functionality. Add native features (push, share, camera) via web APIs to strengthen your case. |
| Microsoft Store | $19 one-time (individual) | Most permissive |
Critical: save your Android signing key
Section titled “Critical: save your Android signing key”When PWA Builder generates an Android package, it issues a signing.keystore file. Save this somewhere safe — Google Play requires every future update to be signed with the same key. Lose it and you can’t update your app, only republish under a new package name.
The same applies to iOS provisioning profiles and Windows certificates.
Updating after launch
Section titled “Updating after launch”Most updates don’t require a new store submission. Because the wrapped app loads from your published Proyecta URL, content and functionality changes are live the moment you publish. You only need to re-submit a new package when you change:
- App name, icon, splash screen
- Manifest entries the wrapper bakes in
- Native permission declarations
See Update Your Mobile App for details.
Coming soon
Section titled “Coming soon”- In-builder app store wizard — generate icons, splash screens, and store listing copy from your existing branding
- Direct integration with PWA Builder so you don’t have to leave Proyecta
- App store metadata management linked to the builder