Progressive web app development: an app experience straight from the browser

A lean PWA, for example as a calculator, catalog or simple data-capture tool, is possible in the Starter package from €2,500. We build PWAs with user accounts, offline synchronization and integrations in the Professional package from €8,000. Larger platforms are quoted individually in the Enterprise package.

Since no store review is needed, a PWA can go live directly once testing is complete. A simple application is often done in a few weeks; for more complex projects with offline synchronization we plan in milestones. We will discuss the exact timeframe in the initial consultation.

We start with a free initial consultation and a platform check on whether a PWA fits your requirements. Next come the offline concept, development with test versions via link, device testing and go-live.

A PWA is suitable when fast availability, a shared codebase and discoverability via search engines are the priority. A native app makes sense if you need a presence in the App Store or deep device features such as certain Bluetooth or background processes. We advise you based on your specific requirements.

Yes. On the iPhone, a PWA can be added to the home screen and launched full screen. Some features are limited on iOS, however, and push notifications require that the app has been added to the home screen. That's why we always test your PWA on real iPhones too.

Yes. With tools such as Capacitor, a PWA can be packaged as an app for iOS and Android and extended with native features. The store guidelines apply here – Apple, for example, expects an app to offer more than a plain website view. If needed, we plan this step in from the start.

A PWA (progressive web app) is a web application that behaves like an installed app. A web app manifest defines icon, name and fullscreen launch, while a service worker caches content so the application loads quickly and stays usable offline. The foundation is web technologies such as HTML, CSS and JavaScript, delivered over an encrypted HTTPS connection.

Often yes, because one codebase serves smartphone, tablet and desktop, and store submissions and developer accounts with Apple and Google are not needed. Updates are also available to all users immediately. We check in advance in the platform check whether a PWA meets your requirements – if you need deep device features, a native app can be the better choice despite higher costs.

Often yes. If the website is built on modern technology, we add a manifest, service worker and an offline strategy so that it can be installed like an app. For older websites, we first check whether the conversion is worthwhile or whether individual areas should be rebuilt. A prerequisite for a good app feel is that the website loads fast on mobile and is clearly usable.

On Android and in desktop browsers such as Chrome or Edge, the browser usually offers installation directly or via the menu. On the iPhone, users open the PWA in Safari, for example, and choose “Add to Home Screen” in the share menu. On request, we display a short guide in the application so your users don't miss this step.

Both are based on the same web technologies and are reachable via an address. A PWA, however, can be installed on the home screen, launches fullscreen without a browser bar, works even on a poor connection thanks to caching and – depending on the device – can send push notifications. Public content remains discoverable through search engines, just like on a website.