PWA & mobile app development: one app for iPhone, Android and the web.
A progressive web app (PWA) is a mobile app that starts right in the browser and installs on the smartphone like any other app. With Capacitor, Sidora AG publishes the same app in the App Store and on Google Play and controls the smartphone’s hardware: GPS, camera, Bluetooth, NFC and push notifications.
One PWA instead of two apps.
A progressive web app, or PWA, is a web application that people install and use on their phone like an app. Your customers expect exactly that: fast, simple workflows on a phone as much as on a desktop.
Separate apps for iPhone and Android cost twice: in development, with every update and in maintenance. A PWA is built from one codebase, runs on every device and updates without app store approval. With a headless architecture we connect your CMS, ERP or shop through APIs, so the solution stays maintainable and extensible.
Below you will see when a PWA is enough, when a native app is the better choice and what concrete benefits your company gains.
“Mobile is no longer an extra channel. For many customers, it is the first contact with your brand.”
What is a PWA
Progressive web apps (PWAs) are web applications that behave like installed apps on a smartphone, yet are built with web technology and open from a regular web address. They run on iPhone, Android and desktop from a single codebase and install from the browser onto the home screen.
Five building blocks supported by current browsers make this work. For your business, that means one development instead of two, updates without store approval and content that search engines can find.
- Web app manifest
- A small file with name, icon, colours and start address. It defines how the app looks and launches once installed.
- Service worker
- A script between the app and the network. For every request, it decides whether the answer comes fresh from the network or from local storage.
- Offline cache
- Views, data and files are stored on the device. With a weak signal the app stays usable, and entries are held locally and sent later.
- Push notifications
- Alerts about jobs, appointments or status changes reach users even when the app is closed. On iPhone, once the PWA sits on the home screen.
- Installation without a store
- Users add the app directly from the browser. It opens full screen with its own icon, without an address bar and without a detour through an app store.
What makes a PWA cost-effective
A PWA saves where native apps create double effort: it is built once, maintained once and shipped once. How large the difference is in your case depends on the feature set. The four criteria show where it comes from.
-
One codebase instead of two
The same application runs on iOS, Android and desktop. Features, tests and bug fixes are done once, not per platform.
-
Updates without store approval
New versions go live through a deployment and are available the next time the app starts, without review by Apple or Google.
-
Installation without a store
No developer account with Apple or Google, no publishing fee, no download detour: a link is enough and the app sits on the home screen.
-
Shareable by link and findable
Every view has its own address. It can be shared by email or QR code, and Google can index public content.
“One codebase for every device. And no update waits for app store approval.”
PWA or native app
In most cases you do not have to choose at all. We build your application as a PWA and bring the same code to the App Store and Google Play with Capacitor. Capacitor wraps the web app in a native shell, so it controls Bluetooth, NFC, camera and sensors, even in the background, and the store becomes an additional sales channel.
A fully native app is only needed when
- tracking has to work without gaps, for example when locating vehicles
- certain functions have to be implemented 100% natively
| Criterion | PWA with Capacitor | Native app |
|---|---|---|
| Development | Advantage: One codebase for web, iOS and Android | One app each for iOS and Android |
| Publishing | Advantage: Web instantly, store app after review | After store review |
| Updates | Advantage: Web app for everyone on next launch | Depends on how users update |
| Discoverability | Advantage: Google search, links and app stores | Advantage: App store search |
| Installation | Advantage: From the browser or from the store | Download from the store |
| Hardware access | Advantage: Bluetooth, NFC, camera and sensors via Capacitor | Advantage: Full, including Bluetooth and NFC |
| Background tasks | Advantage: Sync and notifications in the store app | Advantage: Extensive, including gapless tracking |
In the browser, iOS supports PWAs with limitations: push notifications only from the home screen (from iOS 16.4), no automatic install prompt, and neither Web Bluetooth nor background sync in Safari. As a store app built with Capacitor, these limits disappear because the app runs in a native shell on the device.
We build our store apps with Capacitor 6 on top of Vue 3.5. The web app, iPhone app and Android app come from the same code, so we develop new features once for every channel.
Headless PWAs on your existing systems.
A headless PWA pulls content and data through an API from the systems you already use: TYPO3 or WordPress, your ERP and your shop. Because frontend and backend are separate, we keep developing the app without rebuilding your core systems. The same API also serves your website and third-party systems.
-
Existing systems stay in place
CMS, ERP and databases keep running as before. The API reads data from them and writes orders back.
-
One data logic for every channel
Website, PWA and third-party systems use the same interfaces instead of maintaining content twice.
-
Renew the app independently
A new app design or an extra feature does not require changes to the backend.
AI features built into your app.
AI features can be built directly into a PWA or mobile app: a search that understands your internal documents, content that adapts to the signed-in user, and a support assistant in the same window. The app does more than display content, it thinks along.
More on AI solutions-
A question in everyday language is enough: the app searches manuals, policies and product sheets and answers with a reference to the source.
-
Home screen and notices adapt to the person who is signed in, for example to their role or their previous requests.
-
An assistant answers recurring questions directly in the app, such as the status of an order, and takes load off your team.
PWA development in five steps.
At Sidora AG, a PWA is built in five steps: analysis, concept, development, testing and operation. We start with your business model, not with technology. Each step ends with a result you review before the next one begins.
-
Analysis
We clarify who will use the app, in which situations and which workflows it should simplify.
Result Goals and requirements
-
Concept
We sketch screens and navigation and define which data reaches the app through which interfaces.
Result UX concept and architecture
-
Development
We build in short agile sprints. After each sprint you test a working version on your own device.
Result Working app
-
Testing
We test the app on iPhone, Android and desktop, in offline mode and on slow connections.
Result Tested release
-
Operations
After rollout we ship updates directly, without app store review, and keep the app technically up to date.
Result Ongoing maintenance
PWAs and apps for your industry.
A PWA pays off wherever people work, shop or book appointments on the move: no app store, offline access and push notifications. Whether field service in industry or guests in a restaurant, we shape the app around how your industry uses it. The examples show a typical use case for each industry.
-
Financial Sector & Trust
Secure mobile banking interfaces and client portals. Push notifications for market data, offline access to portfolios and biometric authentication.
Use casePhotograph receipts on the go and send them straight to the fiduciary -
Healthcare & Pharma
Patient apps with appointment management, medication reminders and health diaries. PWAs for clinics with offline-capable information portals.
Use caseReschedule appointments and get reminders to take medication -
E-Commerce & Retail
Mobile shopping experiences with app-like performance without the App Store. Push notifications for offers, offline cart and fast loading times.
Use caseFill the cart without a signal, the order goes out once you are back online -
Industry & Field Service
Mobile applications for field service and maintenance teams. Offline-capable checklists, photo documentation and real-time synchronisation with ERP systems.
Use caseComplete a service report in the basement offline and sync it to the ERP later -
Hospitality & Tourism
Digital menus, mobile ordering systems and guest apps for hotels. QR code-based experiences and contactless services as PWA.
Use caseOrder at the table via QR code, no app download needed -
Professional Services
Client portals as PWA with project overviews, document exchange and appointment booking. Mobile dashboards for consultants in the field.
Use caseCheck project status and documents in the client portal on a smartphone -
Education & E-Learning
Mobile learning platforms with offline access to course materials. Push reminders, progress indicators and interactive exercises as Progressive Web App.
Use caseDownload course materials in advance and keep learning offline on the train -
Public Sector
Citizen apps for municipalities with issue reporters, event calendars and waste collection calendars. Offline-capable and accessible as PWA without App Store dependency.
Use caseReport damage in the neighbourhood to the municipality with photo and location
App quality without building it twice.
Many companies want an app but shy away from the costs. Because classic apps usually have to be built twice — once for the iPhone, once for Android devices. There is an easier way.
A progressive web app, PWA for short, is a website that feels like an app. You can add it to the home screen, it also works without internet and sends notifications on request — but it is built only once. That saves time and money.
If your app should also appear in the App Store and on Google Play, we take the same PWA there with Capacitor. Together we find the path that fits your plans and your budget.
If you also need special features or connections to other programs, you are in the right place with custom web development.
Frequently asked questions about PWAs and mobile apps.
What management and product owners want to know before an app project, answered briefly. If your question is missing, call us or send us a message.
Tap a question to see the answerA PWA (Progressive Web App) is a web application that behaves like an installed app. It runs in the browser, can be added to the home screen without an app store, keeps working without a connection thanks to a service worker and can send push notifications. Because a single codebase serves iPhone, Android and desktop, Sidora AG builds and maintains a PWA with less effort than two native apps.
A PWA suits SMEs and larger companies that want to make customer portals, ordering and booking systems, B2B platforms or internal tools available on mobile devices. It pays off above all when the application should run quickly on every device and get by with a single codebase. If it needs Bluetooth, NFC or a place in the App Store, Sidora AG also releases the same PWA as a store app with Capacitor.
A native app is only the better choice when tracking has to work without gaps, for example when locating vehicles, or when certain functions have to be implemented 100% natively. For everything else, Sidora AG builds a PWA and brings it to the App Store and Google Play with Capacitor 6 on top of Vue 3.5. The app then controls Bluetooth, NFC and sensors even in the background, and the web app and store app share one codebase.
Yes. Sidora AG packages the same PWA with Capacitor as an app for the App Store and Google Play. Your customers find it there like any other app, and it uses the smartphone's features: camera, location, Bluetooth, NFC, Face ID and push notifications. The browser version and the store app share one codebase, which keeps development and maintenance effort low.
At Sidora AG, a PWA or business application starts at CHF 15,000. The exact price depends on features, integrations and security requirements: a customer portal connected to your ERP takes more effort than a simple booking app. Separate native apps for iPhone and Android cost considerably more because two apps are built. After an analysis meeting you receive a quote that sets out scope and stages.
A simple PWA can often go live after a few weeks, while complex platforms and business applications take several months. The duration depends mainly on the feature set, the number of connected systems and how quickly your data is available. Because Sidora AG develops in modules and sets clear priorities, a first version is usable early and is then expanded step by step.
Yes, a PWA can work without an internet connection. A service worker stores pages and data on the device, inputs are saved locally and synchronised automatically as soon as the connection is back. Which features must be available offline depends on the use case: a service report in a basement needs it, a news feed hardly does. Sidora AG clarifies this with you during the analysis.
Yes, a PWA can connect to existing websites, CMS such as TYPO3 or WordPress, ERP systems and online shops. Sidora AG uses a headless architecture for this: the app gets content and data through interfaces while your core systems keep running unchanged. This also lets an existing platform grow into a PWA step by step, without having to rebuild everything.
A PWA can be run as securely as any modern web application. It always runs over HTTPS, sign-in and role-based permissions control access, and sensitive data stays in your systems behind a secured API. This makes PWAs suitable for internal applications and confidential customer data as well. Sidora AG defines the specific security requirements together with you, including the requirements of the Swiss data protection act (FADP).
Let us plan your app.
Tell us who will use your app and which workflows it should simplify. We tell you openly whether a PWA is enough or a native app is needed, and outline a first step.
Request advice