Web App.

The line between a website and a web app is fluid, but it can be drawn with one question: does the user mainly read, or do they work? A company website informs and leads to an enquiry. A web app lets users capture, edit and analyse data — a customer portal, a booking system, job scheduling, a quote generator or an internal dashboard. Webmail, online banking and project management tools are well-known web apps.

Compared with a native app installed through an app store, a web app has clear advantages: it runs on any device with a browser, needs no approval from Apple or Google, and updates are available to everyone immediately. Using the techniques of a Progressive Web App, it can be installed on the home screen, send push notifications and work partly offline. Native apps keep the upper hand where deep device access, high graphics performance or a presence in the app store matter.

Technically, a web app consists of a front end that runs in the browser and a back end with database, user management and interfaces. On top of that come roles and permissions, notifications, exports, logging and security — topics an informational website does not have. That is why building a web app takes considerably more effort than a website, even if the interface looks simple.

For SMEs a web app pays off above all where Excel lists, paper forms or many unconnected tools currently carry a process. The step-by-step route has proven itself: first a clearly defined core process as an MVP, tested in everyday use, then expanded. That way real user feedback flows in before large budgets are committed. When a native app is needed instead of a web app is shown in the comparison on the app development Zurich page.