PWA support

Feature Request
21

That would be really interesting

22

This is a website under construction where I asked AI to create the PWA:

image
image1920×970 138 KB

4 Likes
23

To help me convince the Wappler Team to support this request, the following was composed by Copilot:

Feature Request: Guided PWA Setup Workflow in Wappler

I'd like to propose a streamlined method for building Progressive Web Apps (PWAs) directly within Wappler—one that aligns with modern standards and empowers developers to deliver installable, offline-capable experiences with minimal friction.

PWAs are increasingly vital for mobile-first and resilient web applications. Wappler’s visual power and flexibility make it an ideal candidate for simplifying their setup. Here's a breakdown of the proposed workflow:

:wrench: Core Components

  1. Manifest File Generator

    • Auto-create manifest.json with editable fields: name, short_name, start_url, display, theme_color, icons, etc.

    • UI form for uploading icons and previewing across device sizes

  2. Service Worker Builder

    • Visual interface for caching strategies (static assets, dynamic content, offline fallback)

    • Option to use Workbox presets or custom scripts

  3. HTTPS Enforcement

    • Automatic detection and warnings if the app isn’t served over HTTPS

  4. App Shell Scaffolding

    • Template layout for app shell architecture

    • Lazy loading support for dynamic content regions

  5. Install Prompt Handling

    • Toggle to enable/disable install prompt

    • Customizable install banner with branding options

  6. Validation & Testing

    • Since Lighthouse’s PWA audit has been deprecated in Chrome DevTools, Wappler could offer:

      • CLI-based Lighthouse integration

      • Installability checks via manifest + service worker validation

      • Optional integration with PWABuilder or similar tools

:puzzle_piece: Bonus Suggestion: PWABuilder Studio Synergy

For developers who prefer a visual scaffold or want to validate their PWA setup externally, PWABuilder Studio—a VSCode extension—offers manifest editing, service worker generation, and packaging for app stores. While designed for VSCode, many of its features could be adapted or referenced within Wappler’s UI. Even a lightweight bridge or export/import workflow could help Wappler users validate and enhance their PWAs without leaving the platform.

This could also serve as a fallback for developers navigating Lighthouse’s recent changes, offering a more consistent validation path.

:light_bulb: Why It Matters

This feature would:

  • Lower the barrier for developers new to PWAs

  • Encourage best practices across Wappler projects

  • Expand Wappler’s reach into mobile-first and offline-first development

I’d be happy to assist with testing or refining this workflow. Thanks for considering this enhancement—and for continuing to make Wappler a powerful platform for modern app development.

Best regards,
Ben Pleysier

PS: This is what PWABuilder Studio looks like in VSCode:

image
image490×1191 41.6 KB

5 Likes
24

Hard to believe its been 6 years since this was requested and nothing has been done towards it. It’s becoming more and more important every day.

2 Likes