iOS opens its doors to Progressive Web Apps

We previously presented the cornerstone of Progressive Web Apps, or in other words the key element that allows them to provide the user experience that they do: Service Workers, which are the technical basis of what differentiates PWA's from classic websites. 
This script, run in the background of the browser, offers a number of development possibilities, allowing an app's behavior to be significantly modified. Without Service Workers, Progressive Web Apps wouldn't be able to keep all of their promises, which is where the roadblock caused by the incompatibility between Service Workers and iOS came up.

With the iOS 11.3 update, Apple seems to officially be on board with Progressive Web Apps, as Service Workers are now compatible with iOS!

Since the iOS 11.3 update, we are more than thrilled to announce that your PWA users on iOS can now enjoy the following functionalities:
 

These functionalities are available if the PWA is being run in Safari or directly from the device's home screen (full screen mode). 

Services Workers aren't supported in Web Views, which means in browsers other than Safari (like Chrome iOS or the browser integrated with Facebook, for example). 

On your side, you'll have to make sure that your PWA's generation date is April 6 or after. To verify this, go to the menu Publication > Update > Progressive Web App Engine. Relaunch the generation if the date indicated is older than April 6. 

On your users' side, their devices must work with iOS 11.3 (or a later version). Once the iOS 11.3 update has been installed, your PWA can enjoy all the advantages Service Workers bring. 

Despite the big step forward that this iOS update represents, there are still some functionality differences between PWA's on iOS and Android. Here are the major differences between the two OS:
 

- Cache management: offline functionality in PWA's is possible thanks to a cache management system. On iOS, the data storage is limited to 50Mo, but not on Android. 
On Android, the stored files are deleted if there's no storage space left. On the other hand, on iOS, if the user hasn't used the PWA in several weeks, the cached files are deleted. The data is re-downloaded when the PWA is opened again.

- Background synchronisation: it is possible on Android, but not on iOS.

- Push notifications: they aren't supported on iOS yet. Apple still remains quite silent on the possibility of push notifications being supported in Safari. In any case, no luck for the moment with iOS 11.3.

- On Android, PWA's have Bluetooth access which isn't the case on iOS. 

As of today, developments in favor of PWA's are already underway at Apple.

After Service Workers, it seems like Apple is working on supporting the Web App Manifest in its browser, which is a major element of PWA's. This descriptive file allows for elements used while the PWA is working in full screen mode to be defined, as defined by the W3C. The Web App Manifest in Safari would allow for:
 

Progressive Web Apps already worked on iOS, but they're now on their way to being completely functional on Apple devices. The fact that Service Workers are now supported as well as the Web App Manifest developments that are underway are a good sign for the relationship between Apple and PWA's. 

One of the undeniable advantages of Progressive Web Apps is their accessibility. As they are run on the web, they're accessible via a simple URL, indexed by search engines, and once installed on the home screen, used just like any other app. 

The first two points are more than positive for your visibility outlook, but the last one is crucial. A new distribution channel other than the App Store is now at your disposal. The World Wide Web—open and free.