Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Progressive Web Apps: When a PWA Beats a Native App

Progressive web app development is the option most UK buyers dismiss in the first ten minutes of a project and rediscover eighteen months later, once the second native codebase has quietly eaten the budget. It gets dismissed because almost everything written about it falls into one of two camps: advocacy that skips the parts iOS refuses to do, or scepticism inherited from 2019, when the platform…

Progressive web apps (PWAs) are gaining traction as a cost-effective alternative to native apps for UK businesses. Initially overlooked in favor of native development, PWAs are now recognized as viable options when considering user base, application purpose, and discovery methods.

Key factors influencing the decision between a PWA and a native app include user platform distribution, application functionality, and user acquisition sources. PWAs struggle in scenarios requiring background location tracking, home screen widgets, Bluetooth integration on iPhones, or in-app billing.

A PWA is defined as a web-based application that offers a native app-like experience across multiple platforms using a single codebase. It is installable, operates offline, and integrates with the operating system. The technical requirements comprise three core components: a web app manifest, service worker, and HTTPS support. The manifest provides essential app information, the service worker enables offline functionality and push notifications, and HTTPS ensures secure communication.

The installation process varies across platforms. Android and desktop Chrome offer the most seamless experience, with apps appearing on the home screen, in the app switcher, and in the Play Store. iOS and iPadOS installations occur through the Share sheet, lacking in-page prompts or automatic detection. Desktop platforms provide a more consistent installation experience.

Service workers, crucial for offline capabilities and push notifications, have seen improvements in Chrome's implementation. Installation eligibility no longer mandates a service worker with a fetch handler, allowing developers to create installable apps without offline functionality initially.

The cost-saving advantage of PWAs lies in the reduced development effort, translating to £40,000 to £120,000 in UK terms. While PWAs face limitations in certain areas, such as background execution and certain hardware functionalities, their ability to run on multiple platforms, offline functionality, and integration with operating systems make them a compelling choice for many businesses.

Rewritten by urgent.news; may contain errors — check the original.

Source: dev.to

Read the original at dev.to →

Report a problem with this story

More in Tech

Fix: Codex CLI zstd Compression 400 Error

Originally published on DebugRadar . Fix: Codex CLI zstd Compression 400 Error Quick Fix Summary Problem: Codex CLI requests fail with a bare 400 {"detail":"Bad Request"} on…

More from Sunday 22 November →