Why Safari Still Lags Behind: Hidden Costs for Web Developers

Safari: The New Browser Developers Hate

After Internet Explorer became obsolete, Microsoft introduced Edge, but the crown for the most frustrating browser quickly passed to Apple’s Safari. Developers find Safari’s support for modern Web APIs and features consistently lagging behind Chrome, Edge, and Firefox, making it hard to deliver a uniform product experience.

Progressive Web Apps (PWA)

PWAs allow developers to build web applications that feel like native apps, offering features such as full‑screen operation, OS‑level notifications, offline functionality, local data storage, home‑screen icons, and access to hardware like cameras and microphones.

Major companies such as Starbucks, Twitter, and Uber have adopted PWAs as their primary delivery method.

Apple restricts many PWA capabilities in Safari—blocking system notifications, home‑screen shortcuts, and other features—citing privacy concerns while protecting its App Store revenue model.

WebRTC Struggles in Safari

WebRTC, essential for real‑time video, audio, file sharing, and screen sharing, arrived in Safari years after Chrome and Firefox, and its implementation remains buggy. Support for codecs like VP9 and image formats like WebP arrived only at the end of 2020, and Apple’s hesitation to adopt AV1/AVIF stems from its financial ties to HEVC and HEIC.

Buggy Updates and Slow Release Cycle

Developers criticize Safari’s irregular update schedule, which is tied to iOS releases rather than a fixed cadence, leading to prolonged periods without critical bug fixes and new feature support.

Potential Changes Ahead

While Safari excels in performance and privacy, its poor Web API support frustrates developers. Ongoing public pressure and antitrust scrutiny may force Apple to broaden Safari’s support for PWAs and modern web standards in the future.