What a progressive web app is
A progressive web app is a website built to behave like an installed app. It opens from a home-screen icon, stays usable on a weak signal through a service worker, and can send notifications once the user allows them. Updates go live when you deploy, with no store release to wait for.
For a buyer the question is the job, not the technology: who opens the tool, how often, and whether it must sit in the App Store and Google Play. A PWA website suits tools people reach from a link, an ad or a QR code.
PWA app, native app or website: which one fits
Three kinds of Malaysian buyer ask us this most often. This is how the choice usually falls:
| Clinic group | School or university | Property launch | |
|---|---|---|---|
| Typical job | Appointment booking, reminders and a loyalty card across branches | Applications, open-day registration and a parent or student portal | Show-unit booking, e-brochure and registration of interest |
| A PWA usually fits when | Patients book from a link or WhatsApp and rarely need the phone hardware | Applicants and parents visit for one intake season, not daily | Interest peaks in launch weeks and arrives from ads and QR codes |
| Native usually fits when | Staff need the camera, Bluetooth or offline records all day | Students open it daily for timetables, payments and campus access | Owners manage defects, handover and community services in one app |
| A plain website is enough when | The goal is information and an enquiry form | Programme pages and an enquiry form cover the need | A launch page and a WhatsApp button cover the need |
Sector detail sits on our healthcare marketing page, with schools covered under education marketing.
When a store listing is essential, our mobile app development service builds native or cross-platform instead.
Offline use and push for booking and loyalty flows
Two PWA features matter most to groups that run bookings or loyalty schemes, and a third keeps the data in one place:
- Offline. A service worker keeps the booking form, membership card or e-brochure usable on a weak signal, and sends a queued request once the phone reconnects.
- Push. Appointment reminders, points updates and launch-day alerts, sent only to people who opted in. On iPhone this needs iOS 16.4 or later and a Home Screen install.
- One record. Bookings and points sync to your CRM and to WhatsApp automation flows, so staff see one customer rather than two.
What drives the cost, and how we build and maintain it
We quote each PWA after discovery and publish no fixed price. Five things move the cost:
- The number of screens and user roles, such as patients, staff and administrators.
- Integrations with the CRM, booking system, payment gateway and WhatsApp.
- Offline depth: read-only pages, or forms that queue and sync later.
- Push rules, segments and who in your team manages them.
- Languages, accessibility work and the upkeep plan after launch.
We run discovery, design the screens with the people who will use them, build against your existing systems, then test on the phones your audience actually carries. Upkeep covers browser changes, security fixes and small requests under our web support and hosting service.
For UEM Edgenta Berhad, a Bursa Malaysia-listed group, the corporate pages we built cut average load time from 4.2 s to 1.6 s after launch, as the UEM Edgenta case study records.