Safari, iOS, and Progressive Web Apps: What You Should Know

Safari, iOS, and Progressive Web Apps
Jessica Krywosa

Marketing Director

Jessica Krywosa

Progressive Web Apps (PWAs) are gaining in popularity due to their ability to send push notifications, add to homescreen prompts, and provide offline content, with one build for all devices. Since PWAs focus on the browser and are device agnostic, they allow for seamless adoption by all users, while cutting costs and maintenance for businesses. Outcomes for implementors like include triple the conversion rates, 38% improvement in page load times, and 160% increase in sessions.

A lot of the functionality that PWAs provide is due to the addition of Service Workers. Currently, Chrome, Opera, Firefox, Samsung internet, and Edge all support or plan to support, service workers. But many still feel unsure about adopting PWAs due to the lack of full-throated support for service workers—and PWAs–from Apple.

Interested in transitioning to a Progressive Web App but unsure about implementing one without Safari/iOS support? Here’s what you should know before making a decision.

What about PWAs doesn’t Safari/iOS readily support?

As of today, Safari/iOS does not support Service Workers or Web App Manifests. Without these, many forward-thinking components of PWAs will not work as intended including push notifications, homescreen installation, and offline mode. UPDATE: Work on Web App Manifest in Web Kit has Begun.

Are there any browsers that support PWAs on Apple mobile devices?

Sadly, no. Browsers like Chrome that do readily support all aspects of PWAs are really only re-skinned versions of Safari on iOS devices.

So, if my primary mobile audience is Apple users, why would I implement a PWA?

Even without this support, PWAs still work, just not as they were originally envisioned and require workarounds. You can still manually add homescreen installation, for instance, using ember-web-app. And, while you can implement OS X push notifications from your website using Apple’s developer guides, this does not solve the issue for iOS. One inelegant solution is to wrap the PWA in a native app to gain initial approval for notifications. Offline content is a harder issue to solve, though the other enhancements can be combatted while we anxiously await iOS support.

Documented early adopter outcomes actually show that not only do PWAs work across all browsers, but they actually convert higher than non-PWA sites. Since Progressive Web Apps were built to be lighter they automatically perform better via mobile even without the added enhancements. Lancome recently opted to upgrade to a PWA instead of developing a native app to be able to both serve current customers and reach new users. Even without iOS support they still saw iOS sessions increase by 53% and overall conversions increase by 17%.

Will Apple adopt?

Indications look positive. Webkit shows that both Service Workers and Web App Manifests are either ‘in development’ or ‘under consideration’, with the former given specific mention in the five-year plan. Speculation is that Apple could be slow to adopt due to their current reliance on apps and the App Store. Why promote technology that may eat into that owned pipeline? With Samsung, Google, and Microsoft currently running with this functionality, Apple may be hedging their bets. And with PWAs meaning an easier, single point of contact with consumers, will apps soon be a thing of the past?

Curious about what it would take for your company to upgrade to a Progressive Web App? Let’s talk.


Stay in the Know

Get the latest news and insights on Elixir, Phoenix, machine learning, product strategy, and more—delivered straight to your inbox.

Narwin holding a press release sheet while opening the DockYard brand kit box