One Codebase. One Server. PWA for Internal Systems.

Many companies assume they need separate apps for every operating system. It is an expensive, fragmented way to build. For internal systems, the logic is hard to beat: one codebase, one server, one system that follows the user from phone to desk.

3 min read5 sectionsMay 1, 2026

The expensive way most teams build internal apps

A service business owner needs a technician app. The default thinking goes: hire iOS developer, hire Android developer, hire web developer, build three apps, sync data between them, ship updates through three different review processes.

For a tool used by 15 technicians, this is overkill. A single-platform native MVP commonly runs $30,000-$60,000, and you double that to cover both iOS and Android, on top of 15-25% of the build cost every year just to keep two codebases patched. You spent 3x the money to build, 3x the money to maintain, and you ship updates days slower because Apple has to review every change.

The cost is not just money. It is the time between identifying a workflow problem and having the fix in technicians' pockets. Native app store review still adds 1-3 days to that loop, sometimes more on a rejection. For internal tools, that loop should be measured in minutes. The vendor 30% revenue cut is moot for an internal app, but the submission process, the review delays, and the version-rollout lag are pure friction you do not need to pay.

What PWA actually means in 2026

A PWA is a website that behaves like a native app. It installs to the home screen, runs offline, sends push notifications, accesses the camera and GPS, and feels indistinguishable from a native app to the technician using it.

Under the hood, it is just a website. One codebase in React or whatever stack the team uses. One server hosting it. The browser provides the native-feeling shell. Service workers cache the app so it loads and runs without a connection; most teams use Workbox (maintained by Google) rather than hand-rolling cache logic, and store offline data in IndexedDB until the device is back online.

In 2026, every modern smartphone supports PWAs natively. Chrome on Android. Safari on iOS (web push since iOS 16.4, March 2023). Edge, Firefox, Samsung Internet, all in. Apple has kept closing the gap: Safari 18.4 (2025) added Declarative Web Push, which delivers notifications without keeping a service worker awake, plus the Screen Wake Lock API for keeping a screen on during a job. With iOS 26, any site added to the home screen now opens as a standalone web app by default via the "Open as Web App" toggle. The "PWA does not work on iOS" complaint is years out of date.

Where PWA wins

Internal tools where you control distribution and the user count is bounded. Field service technician apps. Dispatch boards. Customer portals. Inventory tracking. Field forms. Anything where the core workflow is data entry, review, and communication, which is to say forms and lists, is a strong PWA candidate because the web handles that beautifully.

These all share traits: small user base, high update velocity, no need for App Store discovery, deep integration with existing web infrastructure. PWA is the right choice nearly every time.

The pattern: one React codebase, one Vite or Next.js build, deployed to Cloudflare Pages or Vercel. Service worker (via Workbox) for offline caching. Web Push for notifications. The Media Capture API for photo capture. The Geolocation API for GPS. Updates go live the moment you deploy, the same as any website, with no store review in the loop. Done.

Where PWA does not win

Consumer-facing apps that need App Store discovery. Games. Apps that need deep iOS integrations like CarPlay or HomeKit. Apps that lean on hardware the web cannot reach on iPhone: Bluetooth, NFC, or USB peripherals. Apps that compete on platform-specific UX (the latest Apple animation library, the newest Android Material flavor).

There are real iOS gaps worth naming honestly. Background Sync does not exist on iOS, so guaranteed offline-then-retry data submission needs a workaround or native code. Background and geofenced location tracking are unavailable in any browser. The install flow on iPhone is still manual (Share, then Add to Home Screen) rather than the one-tap prompt Android offers. Plan around these, or go native if any of them is mission-critical.

For most service business internal tools, none of these apply. The tech is already in your pocket; you just need it to work. PWA does that.

The Pineido pattern

When Pineido builds internal tools for service businesses, default to PWA. Why: lower cost, faster updates, single codebase, full feature parity for the use cases that matter.

When we build customer-facing experiences that need App Store discovery, we go native. But for the internal tools that run your operations, simplicity wins. One codebase. One server. One system that follows the user from their phone to their desk.

Digital transformation does not have to mean more complexity. Sometimes the best app is the one that just works everywhere.

Written by

Kostadin Stamboliev

Founder and Imaginator

Founder and Imaginator at Pineido. Practitioner across IT consulting, app and web development, technical SEO, and AI / automation. Ships production code in 30-day sprints with fixed scope and clear ownership.

LinkedIn

Frequently asked questions

Does PWA work on iOS?

Yes. Camera, GPS, and offline storage all work, and web push notifications work on iOS 16.4+ once the app is installed to the home screen. Safari 18.4 added Declarative Web Push, and iOS 26 opens home-screen sites as standalone web apps by default. The main caveats: install is manual (Share, then Add to Home Screen), and there is no Background Sync.

How much does PWA save vs native?

For internal tools, typically 50-70% on initial build cost and 60-80% on ongoing maintenance because you maintain one codebase instead of three.

When should I choose native?

Consumer apps that need App Store discovery, deep iOS integrations (CarPlay, HomeKit), or platform-specific UX competition. For internal tools, almost never.

Can technicians install PWA without App Store?

Yes. Browser prompts to install to home screen. Or send the URL via SMS at onboarding. No App Store account, no review process, no friction.

Get operations insights weekly

Join service-business operators who get one actionable insight on ops, automation, and growth every week.

Checking that you're human. You can send in a moment.

No spam. Unsubscribe anytime.

You’re subscribed! Look for our next issue in your inbox.

Ready to ship?

Tell us where you are stuck. We will review it and send a focused recommendation within one business day.