The complexity of adding a Progressive Web App?

[davehakkens]

We're looking into adding a Progressive Web App for the platform.

Why?
Main reason is that we will migrate from our Patreon to our own payment + updates. Meaning we will post more updates a current Patreon users are used to the Patreon App or use mobile for project updates.

What we need to know?

• Understand the full complexity of adding this our codebase, what is needed to build it?
• What does it take to maintain this, and will it make our current development flow more complex?
• Understand what experience we can deliver. For instance can we get mobile notifications?

This topic is to gather thoughts ideas an experiences.

[davehakkens]

Came across this tool for notifications: https://push.foo/

1. Add webapp to your mobile
2. Send notification

Its an example to get push notifications on mobile.
Not sure what it takes to implement but works neat, feels like a native app

ScreenRecording_03-07-2026.07-58-38_1.MP4

[davehakkens]

Gathered a PRO/CON List

Pros

• Installable on home screen — gives the community a more app-like presence without the cost and friction of building native iOS/Android apps or going through app stores
• Push notifications — re-engages users who've installed it, which is the single biggest driver of retention in community platforms
• No extra infrastructure or cost — runs in the browser, fits within your existing Supabase setup, ~$0/month
• Low build effort — 25–35 hours of focused work, well-defined scope, safe to outsource
• Works across all your instances — one codebase change benefits every community automatically
• Zero deployment overhead — baked into your existing build, no new steps in your release process

Cons

• iOS is second-class — Apple's PWA support is better than it was but still lags behind Android. Push notifications only work on iOS 16.4+ and only when installed, which a portion of your users won't do
• Install rates are typically low — most users won't install it, so the impact depends entirely on whether your core engaged users adopt it
• Upfront effort still needed — even outsourced, someone on your team needs to do a code review, handle onboarding the freelancer, and test across devices
• Push notifications add a permission hurdle — users have to actively opt in, and browser permission prompts have low acceptance rates if shown at the wrong moment

The bottom line

It's a low-cost, low-risk way to meaningfully improve retention for your most engaged users — the ones who care enough to install it are exactly the ones worth investing in.