Skip to content

[feature request] Setup first basic progressive web app #4680

@davehakkens

Description

@davehakkens

Is your feature request related to a problem? Please describe.

Users can only access the platform through a browser, with no way to install it on their home screen. This creates more friction for returning users who want quick access, and means we have no path to push notifications for re-engagement in the future.


Describe the solution you'd like

Add basic PWA support so the platform becomes installable on Android and iOS. This first version intentionally excludes push notifications. The goal is just to a working foundation in place.

In scope:

  • Configure a static-asset-only caching strategy (no API/Supabase calls cached)
  • Complete the manifest.json with correct icons, name, theme colour, and display: standalone
  • Make the manifest dynamic from environment variables so each instance (e.g. community.projectkamp.com, community.preciousplastic.com) gets its own branding automatically
  • Track installs and standalone sessions via existing analytics (appinstalled event + display-mode: standalone check)
  • Test install flow on Android Chrome and iOS Safari

Out of scope for this issue:

  • Push notifications (separate issue)
  • Offline content browsing
  • Any changes to existing Supabase API calls or business logic

Describe alternatives you've considered

Building native iOS and Android apps would give a better device integration but at significantly higher cost and maintenance burden, and would require app store distribution. A PWA achieves the installability goal with minimal overhead and no new infrastructure.


Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    New / Under Discussion

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions