Progressive Web Apps (PWA)
Some links on this page are affiliate links: we may earn a commission at no extra cost to you. Our approach
A PWA combines the best of both worlds: the reach of the web and the habits of an app. It avoids the stores, reduces cost and can be deployed continuously. On the other hand, it remains a web application and does not exploit the full hardware potential of the phone. ## When a PWA is enough It suits media, online shops, catalogues, customer portals and internal services consulted regularly very well. The ability to make it work offline is a real asset in areas where the network is irregular. ## When native is still necessary For games, delivery apps with background geolocation, products that rely on the camera or Bluetooth, and services whose presence on the stores is a trust argument, a native app remains the right choice. ## The real challenge: installation A PWA nobody uses is an ordinary website. Success is measured by the proportion of visitors who install it and by their retention. The moment the install prompt is offered, the speed of the first visit and the value delivered from the first opening all need attention.When this guide is for you
- You want a mobile experience close to an app without paying for two native developments
- Your users come back regularly but cope poorly with loading times or weak network areas
- You want to avoid store commissions and approval delays
- You already have a website and want to evolve it into an installable version
- You serve areas where the connection is irregular and offline access is useful
Step by step
- Check the real benefit — Analyse the expected uses: offline browsing, notifications, installation from the browser. If the main need is discovery on the stores, a PWA will not be enough.
- Rebuild as a progressive web app — Make the site responsive, fast and usable offline with a service worker that caches resources and key journeys.
- Installation and notifications — Add the manifest (name, icons, colour, full-screen mode), the install prompt and push notifications where they are supported (very complete on Android, more restricted on iOS).
- Test on real devices — Test installation, offline mode, updating cached data and performance on entry-level smartphones.
- Track adoption — Measure installations, standalone-mode sessions and retention. An installed PWA changes behaviour: encourage users to install it at the right moment.
What it costs (in MAD)
| Service | Indicative price | Good to know |
|---|---|---|
| Converting an existing site into a PWA | 25,000 – 50,000 MAD (≈ 2,300 – 4,600 €) | Manifest, service worker, caching and optimisations |
| PWA built from scratch | 50,000 – 120,000 MAD (≈ 4,600 – 11,000 €) | Mobile-first design, performance and push notifications |
| Push notifications | 5,000 – 20,000 MAD (≈ 450 – 1,800 €) | OneSignal or Firebase integration with consent management |
| Performance and accessibility audit | 8,000 – 20,000 MAD (≈ 730 – 1,800 €) | Lighthouse score, loading time and accessibility |
| Annual maintenance | 10,000 – 30,000 MAD / year (≈ 900 – 2,800 €) | Browser updates, security and enhancements |
Indicative ranges for the Moroccan market in 2026, excluding tax. Prices vary with scope and provider.
Mistakes to avoid
- Promising an experience identical to a native app on hardware features
- Not planning caching of dynamic data: the app shows outdated information offline
- Forgetting that iOS push notifications require the PWA to be installed on the home screen
- Launching without measuring adoption: a PWA is only useful if visitors install it
- Neglecting performance: a slow first visit discourages installation
Frequently asked questions
What is the difference between a PWA and a mobile website?
A mobile site opens in the browser on every visit. A PWA installs from the browser, opens full screen like an app, works partly offline and can receive notifications.
Does a PWA appear in the App Store or on Google Play?
No, it installs from the browser. Google Play recently started allowing PWAs to be published via a wrapper, but this remains marginal; Apple does not allow it.
For which uses is a PWA a poor choice?
For games, apps that heavily use the camera, Bluetooth or biometrics, and services whose credibility comes from a presence on the stores. Access to hardware features remains more limited than in native apps.
How long does it take to convert a site into a PWA?
From 2 to 6 weeks for an existing site that is well structured and sufficiently fast. If the site needs rebuilding or optimising, the work is closer to building a new mobile site.
Does a PWA improve SEO?
Indirectly yes: speed, mobile accessibility and user experience, which are ranking criteria, are at the heart of PWA work. The PWA itself does not add a specific signal.
Updated on
Related guides
Version française: /services/applications-mobiles/pwa/ · AR · NL