Product strategy Kiwi insights
Responsive web app, PWA, or native app: which should you build?
Choose a delivery surface from the workflow, device capabilities, offline expectations, distribution, and support burden before funding separate apps.
The best delivery surface is the smallest one that supports the user’s real workflow reliably. A native app is not inherently more serious than a responsive web app, and an installable PWA is not automatically an adequate substitute for native behavior.
Map the moments of use
Document where, how often, and under what conditions the task happens. Include device ownership, connectivity, session length, input needs, notifications, camera or location use, background work, accessibility, and whether the user arrives from a link or an app store. The workflow should drive the surface.
Understand the practical tradeoffs
- Responsive web app: one linkable release, broad reach, and no installation requirement; often the responsible starting point for account and workflow products.
- Progressive web app: can add install metadata and selected app-like capabilities where browsers support them, but behavior and distribution vary by platform.
- Native app: may be justified by deep device integration, platform-specific experience, intensive offline use, or distribution requirements, while adding separate release, review, and maintenance responsibilities.
Do not use installation as the success criterion
The Web App Manifest specification defines metadata used when presenting and launching installed web applications. It does not guarantee offline behavior, reliable background processing, or access to every platform capability. Prototype the riskiest device and connectivity requirement before committing to the architecture.
Plan identity, updates, and support
Decide how users move between web and installed surfaces, recover accounts, understand offline status, receive updates, and contact support. If multiple clients share an API, define version compatibility and rollout behavior. Count the long-term operating cost, not only the first build.
Kiwi can help test the core workflow and choose an appropriate first delivery surface. App-store policy, specialist mobile security, regulated use, and device-specific assurance require the relevant expertise.