Mobile Apps

Build mobile-friendly web apps in Proyecta. PWAs work today; native iOS/Android wrappers via PWA Builder.

Proyecta builds web apps. The fastest path to “an app on a phone” is a responsive web app — optionally enhanced as a Progressive Web App (PWA) so users can install it to their home screen and (on supported platforms) get push notifications, offline support, and a full-screen experience.

For native distribution through the App Store, Google Play, or Microsoft Store, you wrap the published PWA using a tool like PWA Builder.

What you get out of the box

• Responsive viewport switcher in the builder — flip between Desktop / Tablet / Mobile previews while editing
• Mobile-first AI prompts — the AI knows how to build responsive layouts when you ask
• Push notifications via the Proyecta SDK — see Push Notifications
• Mobile builder UI — Proyecta itself works on phones, so you can build on the go

The PWA path

For most apps, a PWA is the right answer:

Add PWA support to my app:
- Web app manifest with name, icons, theme color
- Service worker with offline cache for the app shell
- Install prompt that appears after the user has visited 3 times

The AI will set up the manifest, service worker, and install prompt. Once you publish, users can:

• Open your app in any mobile browser
• Tap the browser menu and choose Add to Home Screen (iOS) or Install app (Android)
• Launch it like a native app from their home screen

PWAs on iOS 16.4+ also support Web Push, so notifications work — see Push Notifications for setup.

Going deeper: native wrappers

If you need to ship to the App Store or Google Play, the recommended path is to wrap your published PWA:

1. Publish to your *.proyecta.live subdomain (or a custom domain)
2. Open pwabuilder.com and enter your URL
3. Generate native packages — Android (AAB), iOS (Xcode project), Windows (MSIX)
4. Submit to the respective store

See Publish to App Stores for details.

Limits to know

• Apple may reject pure WebView apps that don’t add native functionality. Consider this before targeting the App Store.
• Push notifications on iOS require the user to install the PWA from Safari first (not from a wrapper).
• Camera, GPS, contacts all work via web APIs — native-only APIs (HealthKit, ARKit) aren’t reachable from a PWA wrapper.

Coming soon

• Native React Native / Expo templates for projects that need true native shells
• Capacitor integration as an alternative wrapping path
• In-builder app store publishing wizard (icons, splash screens, store listing copy)
• App store metadata management synced with the builder