A shared Android tablet at a clinic reception usually has two problems a sales demo never shows: storage that is almost full, and an app demanding a Play Store update at 10:15 with nine patients waiting. Nobody at the desk has time to delete photos. That everyday situation is what the PWA doctor portal vs native app question comes down to, and it has less to do with technology preferences than with the phones and tablets a clinic already owns.
A Progressive Web App (PWA) is a website built to behave like an installed app. You open a link, tap "Add to Home screen," and it launches full-screen with its own icon, caches screens for weak connections and can send push notifications. It never goes through an app store, so there is no store review and no waiting for each device to update.
The best-known evidence is old, but it's specific
The case study people cite most often is Twitter Lite, which Google documented on web.dev in 2017. Twitter's PWA was about 600KB over the network, against a 23.5MB download for the Android app, which by Google's count is less than 3% of the storage. First loads on 3G came in under 5 seconds on most devices, repeat visits started in under 3 seconds, and Twitter used web push for more than 10 million notifications a day.
Many blogs blur those two load figures into "under 3 seconds on slow networks." Twitter also had a large engineering team, so the study shows what the web can do, not how quick any clinic vendor's PWA will be.
Why the storage and update points hit clinics harder
Clinic hardware isn't used like a personal phone:
- Shared and old devices. Two receptionists and a visiting physiotherapist may share one tablet, and a four-year-old budget Android often stays on as the billing phone. Every heavy app competes for the same space.
- Doctors work at more than one place. A link works the same at her own clinic in the morning and a nursing home in the evening, even on a device she doesn't own.
- Fixes need to reach everyone today. If a prescription template prints the wrong dosage unit, a PWA picks up the fix on the next page load. On a native app, some devices stay on the old build until someone updates them.
Where a native app still earns its place
For hours with no signal, such as a health camp in a village, an offline-first native app will usually cope better. The same goes for features that lean on device hardware, like continuous barcode scanning for pharmacy stock or Bluetooth medical devices. Browser support for these has improved, but test each one on your own devices.
iPhones need a separate note. Apple only added web push for home-screen web apps in iOS 16.4, released in 2023, and a site opened in Safari still can't ask for push permission. Staff on iPhones who rely on alerts need the portal on their Home Screen.
For the core work of a doctor portal (today's queue, a prescription, the last visit summary, whether a bill was paid), these limits rarely decide the matter.
What ExaHealth puts on those core screens
ExaHealth runs in the browser at app.exahealth.com, and its main screens are the ones just listed. The live queue shows who is waiting and messages patients on WhatsApp when their turn comes up. Open a patient from the list and past visits and uploaded reports are already in view. A prescription can be typed or dictated; each medicine is selected from the built-in catalogue instead of typed freehand, and interaction warnings appear before it is sent. On a shared reception tablet, role-based access lets the receptionist book appointments while clinical notes stay hidden. Run the test below on it with your oldest clinic phone, as you would with any vendor.
A quick test before you commit
Don't ask a vendor whether they "support offline." Hand them your oldest clinic phone and try this:
- Install it. Can you add it to the home screen from a link in under a minute, and does it open without the address bar? Note the storage it uses.
- Turn on airplane mode halfway through a prescription. Is the draft saved or lost?
- Ask for the offline list in writing. Which screens work from cache, and which need a connection?
- Time an update. For a PWA, a fix should reach every user in minutes. For a native app, ask what share of devices are still on the old version a week later.
- Check notifications on both platforms. Send a test alert to an Android phone and to an iPhone with the portal on its Home Screen.
If the "PWA" fails steps 1 and 2, it's probably a mobile website with an install prompt added, which is a different product.
See the queue and prescription screens in more detail on ExaHealth's page for doctors.
If you're still comparing options, read Best Clinic App for Doctors: What to Look For in 2026 next, then Doctor App: What Indian Physicians Actually Use It For.
References
- web.dev: Twitter Lite PWA case study
- WebKit: Web Push for web apps on iOS and iPadOS
- WebKit: features in Safari 16.4
Frequently Asked Questions
What is a PWA doctor portal?
It's a doctor-facing web app that you install from a link instead of an app store. After installation it opens full-screen from the home screen, can keep some screens cached for poor connections, and can send notifications, while running entirely on web technology.
Will a PWA doctor portal send notifications on an iPhone?
Yes, on iOS/iPadOS 16.4 or later, and only once the portal has been added to the Home Screen. A website opened in Safari can't ask for push permission, so staff with iPhones need that extra step when they're onboarded.
What happens to my work if the internet drops?
That depends on how the portal was built, which is why you should test it instead of asking about it. A good PWA keeps recently opened screens and unsaved drafts. A weak one shows an error and loses what you typed. Try turning on airplane mode during a demo.
When should a clinic pick a native app instead?
Pick native when you need long stretches of fully offline work, or a feature that depends heavily on device hardware, such as continuous scanning or pairing with Bluetooth devices. For queue management, prescriptions and patient history, a well-built PWA is usually enough.