Web app development — in the browser, as a PWA, or cross-platform with React Native

A process pilot runs €8,000–20,000 and is in production in 6–12 weeks. A full B2B web app with several processes, interfaces and a permission model runs €20,000–60,000 over 3–6 months. For multi-tenant platforms we quote a fixed price after discovery. Custom web application development at this level is priced for senior staffing throughout, with no junior pass-through. Running the thing is costed separately: €5,000–20,000 once for setup, then €20–50 per month for hosting, €150–400 for a high-availability setup, plus 2–5 hours of support per month. Over three years that operating share adds up to €40,000–80,000 — the build sum sits in front of it, not inside it.

By where the work happens, not by the technology. If people work at a desk and there is neither an offline nor a push requirement, a web app in the browser is enough. If the work happens in the field, in a workshop or in a warehouse where the connection drops, it becomes a PWA. Only when store presence is itself the requirement, or the browser will not expose the hardware you need, does React Native pay for itself. We make that call at the end of discovery, not before it. Getting it wrong is the most expensive mistake in the whole project.

Three things, and we name them before any contract is signed. First, there is no automatic install prompt: the user has to add the page to the home screen through the share sheet, because beforeinstallprompt is not a standard and does not exist in Safari (MDN). Second, push notifications only work after exactly that step; they have been available since iOS 16.4 (WebKit, 2023). Third, Background Sync and Web Bluetooth are missing in Safari and iOS Safari across the board (caniuse, as of 2026). If your project rests on any one of those, we do not build a PWA — we build a React Native app.

No. Apple announced it in February 2024 and reversed the decision before iOS 17.4 shipped: "we will continue to offer the existing Home Screen web apps capability in the EU" (Apple Developer Support, 2024). The opposite claim still circulates in agency blogs. Since iOS 26, every website added to the home screen even opens as a web app by default, with no installability requirements attached (WebKit, September 2025). A different sentence does stay true: on the iPhone, WebKit alone still decides what a web app is allowed to do.

Into Google Play, yes, through a Trusted Web Activity with a manifest, HTTPS and Digital Asset Links. Into the Microsoft Store as well, as an MSIX package. Into the Apple App Store, no: App Review Guideline 4.2 requires functionality beyond a repackaged website. If your application has to be in Apple's store — because that is where buying, distribution or searching happens — the route goes through React Native. The Apple Developer Program costs 99 USD per year for that (Apple, 2026).

That question is answered. The new architecture has been the default since version 0.76 in October 2024, the old bridge was removed in 0.82, Hermes V1 became the default engine in 0.84, and the current release is 0.86 from June 2026. Microsoft Office, Outlook and Teams, Amazon Shopping and Kindle, and the Shopify apps all run on it (React Native Showcase). After its full migration, Shopify reports more than 99.9% crash-free sessions and screen load times under 500 milliseconds at the 75th percentile (Shopify Engineering, January 2025). If you are picking a React Native development company this year, maturity is not the thing to interrogate.

Because one language across every layer removes the translation losses. TypeScript on the front end with Next.js, on the back end with NestJS, in the app with React Native, with Postgres through Supabase and Keycloak for sign-in and roles. The same people can touch any layer without a handover to another team. Agencies that offer React and Angular and Java and Python at the same time have simply not made this decision. They push it into your project instead.

The source code is yours, and the repository is in your company's name from the start. We build on open-source components with no licence fees, running on EU infrastructure at Hetzner. Store accounts for a React Native app are opened under your company, not ours. A documented handover path to your own IT or to another team is part of the delivery. Switching providers must never fail because knowledge sits inside an agency.

First, fixing the delivery model too early — usually on "app" — before anyone has looked at where the work actually happens. Second, adding the offline requirement late: retrofitting local storage, a queue and conflict resolution costs a multiple of planning them in. Third, demanding the app store when nobody needs it, which buys you a review before every update plus the platform deadlines Apple and Google set for you. Fourth, bolting on multi-tenancy instead of designing the data model for it from the first line.

When you need a consumer app with a 3D engine, ARKit or game logic. When the core of your project sits deep in the operating system: wearables, offline mapping, continuous background location or geofencing. When your budget is under roughly €8,000, because a standard tool or a website usually carries that. When an existing SaaS product is to be rebuilt one to one. And when you expect twenty developers by month two — we work senior-first in small teams and scale through scope, not headcount. In those cases another web app development company is the right call, and we will say so in the first conversation.