PWA or native app: what should your first release use?
Choose a delivery approach from the user workflow, not from a preference for a framework. A progressive web app can be a useful option, but it does not make every native feature available in every browser.
List the capabilities the workflow cannot lose
Start with the features that make the product usable: camera access, notifications, location, file handling or background work. Record the actual target devices and browsers, then verify the required behaviour on those environments.
Do not turn “works on mobile” into an assumption that all capabilities behave identically. MDN documents installation and other PWA capabilities with browser-specific requirements; check the current documentation and test the workflow.
Decide how people will reach the product
A web link can connect an invitation, search result or existing website to the application. A distribution strategy that depends on an app store creates a different set of decisions. Installation, updates and how a user returns to the product should be part of the brief.
For a product serving a known customer group, ask how users first receive access and how much instruction is realistic. The answer matters more than an abstract preference for web or native.
Define what happens without a reliable connection
A cached interface is not the same as a working offline business process. Decide which information may be stored on the device, which actions can wait and how a conflict is handled when the connection returns.
- Can the user view previously loaded information?
- Can they create or change data offline?
- Which action must wait for server confirmation?
Prototype the risky capability before choosing
Test one critical workflow on the least capable supported environment. Use that result to decide whether a PWA, native application or a narrower initial scope meets the need.
Our Praktika case describes a first PWA release. It is an example of a project scope, not proof that the same approach fits every product. Bring the device requirements and user journey to a PWA planning discussion.