App development for iOS, Android, the web and large displays, guided by measurable goals and supported well beyond the store launch.
Progressive Web App | Anexia Digital Engineering

The progressive web app as an alternative to store apps.
Does it really have to be an app from the store? Surprisingly often the honest answer is no. A progressive web app runs in the browser, sits on the home screen, works offline and can send notifications. It is shared through a simple link, without review by Apple or Google.
When a progressive web app pays off
We ask the store question in almost every first conversation. Anexia Digital Engineering builds progressive web apps for organisations that want to reach their users quickly and without obstacles, and is just as clear about when this route falls short. Four situations make a particularly strong case for the web.
Reach without friction
Open the store, search, download, wait, open, sign in. Every step loses users. A PWA is there after one click, a huge advantage for services people find through search engines, newsletters or QR codes.
Occasional use
Nobody installs an app for a three-day trade fair or for a retailer they order from once a year. As a web application, the service still gets used.
Internal applications
Installation can be explained once or rolled out through device management. Distribution via a link avoids coordination with the stores, and updates reach everyone immediately.
Found on Google
Search engines can index the content of a PWA, while a store app stays largely invisible to Google. If you want to grow through organic search, the web gives you the better starting position.
What makes a progressive web app
The term does not describe a technology of its own but a website with particular properties. Three building blocks make the difference. Once they are in place, the application can be installed. It then appears with its own icon, starts without an address bar and behaves for the user much like an app from the store.
Service worker, manifest and HTTPS
A service worker is a script that sits between the application and the network. It caches files and data, answers requests even without a connection and receives push messages, even when the application is closed. The web app manifest is a small file containing the name, icon, colours and start URL. It tells the operating system how the application should look once installed. An encrypted HTTPS connection is the prerequisite for the browser to enable these features at all.
What a PWA can do today
Browser capabilities are often underestimated, because many decision-makers still have the state of a few years ago in mind. Today a PWA works without an internet connection using locally stored data. Push notifications work on Android, Windows, macOS and, since iOS 16.4, on the iPhone too. Camera, microphone and location are accessible, and users can sign in with a fingerprint or face recognition via passkeys. Content can be shared through the system dialog, payments run through the Payment Request API including Apple Pay and Google Pay, and the app installs on the home screen or desktop.
For a large number of applications, that is entirely sufficient. Ordering portals, booking systems and customer areas are among them, as are checklists, training content, event guides and internal tools. What matters is that the requirements of your project come before the technology. That is why we first establish which functions are genuinely needed, and only then the route to them.
Limits of a progressive web app on the iPhone
Anyone planning this route needs to know its limitations, or disappointment follows the launch. Most of them concern iOS. Android actively offers users the option to install, whereas on the iPhone they have to find the home screen option in the share menu themselves. Many people do not know this route. A well-made in-app guide helps but never matches the rate of a store download.
On iOS, push only works if the application has first been added to the home screen, and a normal browser tab receives no notifications. For business models that rely heavily on push, this is a significant drawback. Apple also limits local storage, and in a browser tab Safari deletes data from sites that have not been visited for a while. According to Apple this rule does not apply to installed web apps, but there is still no guarantee of persistent storage.
Background sync as Android knows it is not available on iOS, so anyone who wants to keep large amounts of data offline will hit limits here. Bluetooth, NFC, USB and some sensors are available in Chrome but not in Safari. Widgets, watch apps and integration with voice assistants are reserved for native apps. And anyone searching the App Store will not find a web application, even though for some audiences the store is the first and only place they look for an app.
If several of these points are core requirements for you, the route leads to an app in the store. Hybrid app development uses the same web code and adds the missing native features. For higher demands, cross-platform app development or native app development are the options to consider.
In early 2024 Apple announced it would switch off installable web apps in the EU in the wake of the Digital Markets Act, then reversed the decision shortly afterwards following protests. The feature remained. The episode shows that the capabilities of installable web apps on the iPhone depend on the goodwill of a single vendor. We consider the risk manageable, but it belongs in every serious assessment.
How we build a progressive web app

Not every good app needs a store.
From the web to the stores
Measuring the success of a PWA
One advantage of the web is that it can be measured. With a web application you can see from the very first visit where visitors come from, how far they get and where they drop off. No store sits between the advert, the search result and the completed order to break the chain. We set up privacy-friendly analytics and define a small number of meaningful metrics with you. Proven ones include the home screen installation rate, the share of returning users, opt-in to notifications and the completion rate in the most important flow.
Because changes go live without review, you can react quickly. A reworded button, a shorter form or a better-placed installation prompt reaches every user within a day. For products at an early stage, that speed is worth its weight in gold. Some organisations deliberately use their web application as a testing ground before a feature moves into the more elaborate store apps.
The way into the stores stays open
Taking the web route does not rule out the stores. For Google Play it can be packaged as a Trusted Web Activity and submitted as usual, and the Microsoft Store also accepts web applications. Apple is more difficult, because a plain wrapper around a website is generally rejected. Here we rely on Capacitor and add native features, turning the web application into a fully fledged hybrid app. Our page on Ionic app development explains the toolkit behind it.
This sequence is often the right one. First the progressive web app, to get to market quickly and gather real usage data. Then, once the numbers justify it, the store apps from the same codebase. Anexia Digital Engineering has been developing software since 2006 and apps since 2008, with a team of more than 40 specialists in Austria and Germany who can see both stages through.
What a progressive web app costs
Of all approaches it is the most economical, because only one interface is built for every device and the store effort, including review, falls away. On top of that, you pay Apple and Google neither annual fees nor commission on digital sales. As a way into the mobile channel, it is the least expensive option.
Economical does not mean free, though. A well-thought-out offline concept, good performance and proper accessibility take time. The effort for testing in Safari is also often underestimated, because this browser behaves differently from Chrome in some details. Our page on app development costs explains how to plan a budget.
Questions on progressive web apps
Related topics
- App Development
- Kotlin Multiplatform
Write and test business logic once in Kotlin while the interface stays native on iOS and Android. A step-by-step route to less duplicated work.
- App Development Costs
What drives the effort behind an app, which factors push it up and how to plan your budget realistically, well beyond go-live.
- Ionic App Development
Ionic and Capacitor turn your web application into an app for iOS and Android, built on the knowledge your team already has.
- Mobile App Development
React Native and Flutter for cross-platform plus native development with Swift and Kotlin - mobile applications for iOS and Android.
- UX/UI Engineering for B2B Software
Interaction concepts, prototyping in Figma, design systems, usability testing and accessibility to WCAG 2.1 for complex B2B software.
Honest advice. Web or store?
Walk us through your requirements. In a no-obligation initial conversation we will tell you whether a progressive web app is enough, whether it makes a sensible first step or whether you should start straight away with an app for the stores.
