Progressive web apps: the best of web and mobile
Gjethe builds progressive web apps: websites that install to the home screen, keep working offline and send push notifications, from a single web codebase that runs on iOS, Android and desktop. We build new PWAs and convert existing sites by adding a web app manifest, service worker, offline pages and install prompts.
- Free first consultation
- Written quote for your project
- Flexible payment milestones
At a glance
- Runs on
- iOS, Android and desktop
- Install
- From the browser, via a link
- Offline
- Service-worker caching
- Updates
- Instant, no store review
Definition
What is progressive web apps?
A progressive web app (PWA) is a website built with modern browser capabilities, a web app manifest and a service worker, so it can be installed like an app, load instantly, work offline and send notifications.
Not every product needs to be in the App Store. For booking tools, internal apps, content products and customer portals, a PWA gives people an app-like experience from a link: no download from a store, no review process for updates and one codebase instead of three. When a product does need deep device features, we'll tell you and recommend a native or React Native app instead.
Who is it for?
Booking and ordering tools
Customers reorder or rebook regularly and benefit from an icon on their home screen.
Internal business tools
Field teams and staff need an app without the overhead of publishing it in stores.
Content and media products
Readers want fast loading and offline reading on poor connections.
Startups validating an app idea
Test whether people use the product before investing in native apps.
What's included, and what you keep
What's included
- Web app manifest and icons
- Service worker with a caching strategy
- Offline pages and offline-first data where needed
- Install prompts for Android and desktop, guidance on iOS
- Push notifications
- Background sync for forms and actions
- App-shell architecture for instant loading
- Responsive design for every screen size
- Lighthouse PWA and accessibility checks
- Analytics for installs and engagement
What you receive
Handed over at the end. Yours to keep.
- The live PWA on your domain
- Source code in your repository
- Push notification set-up and documentation
- Caching strategy documentation
- Installation guide for your users
PWA or native app?
| Progressive web app | Native app (iOS/Android) | |
|---|---|---|
| Install | From the browser, via a link | From the App Store and Google Play |
| Updates | Instant, no review | Through store review |
| Offline | Yes, with service workers | Yes |
| Push notifications | Yes (on iOS when installed to the home screen) | Yes |
| Deep device access | Limited: Bluetooth, background tasks vary by platform | Full |
| Codebase | One web codebase | One per platform, or shared with React Native |
How does offline mode work?
A service worker sits between the app and the network. When the app is online, it stores the files and data the user needs; when the connection drops, it serves them from that store instead of showing an error.
We choose a caching strategy per type of content. The app shell (layout, styles and scripts) is cached ahead of time so it opens instantly. Frequently changing data uses network-first with a cached fallback, and actions taken offline, such as submitting a form, are queued and sent automatically when the connection returns.
Where PWAs work especially well
Ordering and reservations
Repeat customers reorder from a home-screen icon without downloading anything from a store.
Field and delivery teams
Staff use the app on patchy connections; offline mode and background sync keep work flowing.
Learning platforms
Lessons and materials load quickly and can be saved for offline study.
Customer portals
Clients check orders, invoices or bookings in an app-like experience without a separate mobile project.
What makes a PWA feel like a real app
- Opens instantly from the home screen, even offline
- Navigation that works with thumbs, not just a mouse
- Clear feedback when the connection drops or returns
- Notifications that are useful and easy to control
- No browser address bar in standalone mode
- Smooth transitions between screens
How progressive web apps works, step by step
Every step has a clear output you can review. Timing is agreed in your quote.
- 1
Use-case check
We confirm a PWA fits, or recommend native if the product depends on device features browsers don't offer.
- 2
UX design
App-like navigation, offline states and install moments designed in Figma.
- 3
Build
Web app development with the manifest, service worker and caching strategy.
- 4
Notifications
Push set-up with permission prompts timed to when users see the value.
- 5
Test
Installation, offline behaviour and notifications tested across iOS, Android and desktop browsers.
- 6
Launch
Deployment, analytics and guidance for users on installing the app.
Tools, and what shapes your quote
Pricing is based on your project and agreed in your quote. These are the things that move it.
| Factor | Why it matters |
|---|---|
| New build or conversion | Adding PWA features to an existing site costs less than building an app from scratch. |
| Offline requirements | Read-only offline is simpler than full offline editing with sync. |
| Push notifications | Notification logic, segments and permission flows add work. |
| Accounts and data | Logged-in experiences need authentication and secure data handling. |
| Integrations | Payments, booking systems or back-office tools add development. |
| Area | Tools |
|---|---|
| Frameworks | Next.js, React, Vue / Nuxt |
| Service workers | Workbox, custom service workers |
| Push | Web Push, Firebase Cloud Messaging |
| Testing | Lighthouse, Chrome DevTools, real devices |
Common mistakes to avoid
What we see go wrong most often, and how a good project avoids it.
Asking for notifications immediately
A permission prompt on the first visit is usually declined. Ask after the user sees why notifications help.
Caching everything forever
Overly aggressive caching serves outdated content. Each type of data needs its own strategy.
Ignoring iOS behaviour
Installation and notifications work differently on iPhone. Users need clear guidance to add the app to their home screen.
Choosing a PWA for hardware-heavy apps
Products built around Bluetooth, background location or deep OS integration belong in native apps.
Frequently asked questions
Do PWAs work on iPhone?
Yes. iPhone users add a PWA to the home screen from Safari's share menu, and installed PWAs can receive push notifications on recent iOS versions.
Can a PWA be listed in app stores?
Google Play accepts PWAs packaged as Trusted Web Activities. Apple's App Store generally requires a native wrapper that offers real app functionality.
Can you turn my existing website into a PWA?
Yes. We add the manifest, service worker, offline pages and install prompts, and adjust navigation so it feels app-like.
Is a PWA cheaper than a native app?
Usually, because one web codebase serves every platform and updates don't go through store review. The difference shrinks if you'd build with React Native anyway.
Can a PWA take payments?
Yes, through standard web payment providers such as Stripe, including Apple Pay and Google Pay in supported browsers.
How do users find and install the PWA?
Through your website, a link or a QR code. On Android and desktop the browser offers to install it; on iOS we show a short guide.
Will it be indexed by Google?
Yes. A PWA is still a website, so its public pages can be crawled and ranked like any other.
Can the PWA work with our existing backend?
Yes. The PWA is a front end; it can use your existing APIs, CMS or database, or we can build the backend alongside it.
Can a PWA use the camera or location?
Yes. Modern browsers allow camera, microphone and location access with user permission. Some deeper capabilities, such as background location or Bluetooth on iPhone, still require a native app.
How do updates reach users?
When we deploy a new version, the service worker picks it up on the user's next visit, so everyone gets the latest version without visiting an app store.
Do PWAs work on desktop computers?
Yes. Chrome and Edge let users install a PWA on Windows, macOS and ChromeOS, where it opens in its own window like a desktop app, useful for internal tools and dashboards.
Related services
Progressive Web Apps by industry
Build your PWA.
Tell us what you need. You get an honest assessment, a clear plan and a written quote. The first consultation is always free.
- What happens next
- 1You tell us what you need
- 2We aim to reply within 24 hours with questions
- 3You get a written quote for your project