Ask HN: Who has had a successful PWA product?

Hacker News Discussion ↗

Progressive Web Apps (PWAs) attract interest as a way to build once and run across platforms, but many developers report severe reliability and UX issues, especially on iOS where Safari’s data deletion, limited APIs, and awkward install flows can quietly break apps or confuse users. Several successful or at least sustainable PWAs are cited — from games and drawing tools to messaging and finance apps — yet most agree their success comes from product-market fit rather than the PWA tech itself. A recurring theme is that users overwhelmingly expect “real apps” in app stores, leading many teams to ship thin native wrappers around web apps or prioritize native development, while a minority still argues for PWAs as a long‑term bet on the open web despite current platform and distribution hurdles.

Product vs. Technology Choice

  • Several comments stress starting from user needs, not from “I want to build a PWA.”
  • PWA is framed as one delivery option among many (webpage, native app, even hardware).
  • Distribution is emphasized: first‑time founders focus on product, second‑time founders on distribution.

Platform Limitations and Data Loss

  • Multiple reports of iOS Safari randomly wiping local data (cookies, localStorage, IndexedDB, push tokens), especially under disk pressure or due to bugs.
  • Some argue this is intentional hostility to PWAs; others blame general iOS/Safari bugginess and lack of incentives to fix low‑incidence issues.
  • Android/Chrome is also reported to randomly delete PWA data, even with “persistent storage” APIs.
  • Consequence: apps relying on client‑only data (e.g., large IndexedDB datasets) face serious reliability issues.

Workarounds and Architectural Choices

  • Suggestions include:
    • Keep authoritative state on the server; use client storage mainly as cache.
    • Use URL tokens instead of cookies for session continuity.
    • Avoid heavy reliance on fragile browser storage; design with reset in mind.
    • Instrument detailed logging to detect data nukes.
  • Some devs wrap PWAs with Electron/Cordova/Capacitor/Tauri to reach app stores and get more reliable storage APIs.

Discoverability and App Store Dynamics

  • Users commonly expect to “find it in the App Store.” PWAs alone generate confusion and complaints.
  • iOS PWA install UX (“Add to Home Screen” via Share menu) is seen as obscure and a major adoption barrier.
  • Android is friendlier; publishing PWA‑based apps to Play Store is relatively easy.
  • App stores add friction (reviews, revenue share) but also trust, billing, and discoverability.

User Preferences and UX

  • Many users strongly prefer native apps, or at least something installed from an app store.
  • Some accessibility‑focused comments say PWAs and “progressive” web UIs often have worse UX than native.
  • Others argue users just want things that work and are being funneled toward native apps by platform policies.

Examples of PWAs in Practice

  • Multiple successful or at‑least‑sustainable PWAs are mentioned: drawing tools, solitaire games, messaging clients, personal finance tools, vocabulary/spaced‑repetition apps, social/NSFW apps, and major platforms (social networks, dating, video conferencing).
  • Common themes among “successful” PWAs: simple offline‑friendly use cases, strong core utility, and often minimal reliance on advanced PWA APIs.