Some time ago, I’ve written an article on the PWI experience on beta versions of iOS 12.2 and in this video I want to share some of my findings with you. My name is Tom, and today’s episode of white belt progressive Babbitt, is focused on. Why now is a good time to start building progressive web apps for iOS [, Music, ]? Well Peter BAE’s work on IRS.

They require the user and the developer to jump through a few extra hoops to get that installed. Full screen experience, luckily, with the latest baddest of iOS 12.2. The situation has improved a fair bit in this episode. I want to highlight some of the improvements that have been implemented and talk about still existing limitations. You can also read all the details in the linked article. Unfortunately, iOS doesn’t support the before installed prompt event and doesn’t have an add to homescreen prompt or banner like Android.

However, I, as users has been able to use the Add to Home screen button in Safari. Share sheet for ages, weber manifests support, is under development and only partially supported in Safari, which means for icons and spread screen. You still have to rely on the old-school Apple web, app link, relations, apple touch, icon and apple touch, startup image for app icons and spread screen or just use. Pwi, compare a small library that reads the web app manifest and on iOS at the right set of meta tags, creates the icons and generates a splash screen image for you in scope and out of scope.

Navigation works properly now, which means POS, remember the previous state. When restarted now, when you open an out of scope, link like the office page in the philic ad sample app, it opens the page in a full screen in a browser, rather than kicking you out of the app completely and you’re right back in the app where You were before when you multitask away from a PWA.

The state will be preserved when you return before Safari would reload the PWA and lose the stain entirely. It’S not perfect yet and there’s currently a short delay, but it is way better than it used to be. Apple has also introduced navigation, swipe gestures, so now they can swipe back and forth from the left and right of the screen just like in native applications. These gestures are still new, amen, be obvious to everyone, so it definitely makes sense to show an in-app back button.

You can attack if your app is running in standalone mode without URL bar at the top and without a button bar at the bottom. By checking the proprietary, navigator, dot, standalone property, the standard display mode media – query that you would use.

Usually it’s not supported yet, but you can combine the two approaches in one call. Personally, I’m really excited about the new web share API, which makes it easy for pwace to share content with other installed apps using the iOS share sheet Twitter editors to their PWA, and I use it a lot if there’s a tweet, I want to follow up with Later I shared with myself via email and can then respond to it later.

In this episode, I focused on new PWI capabilities on iOS and whether there’s still room for improvement, I’m extremely excited about the progress apples made in the latest betas. You can have Apple prioritize. The features they work on by detailing your use cases and comments on the PWI specific box that I’ve collected in my article. I hope to see you again in the next episode of Weibull progressive web apps, where I will talk about offline analytics with word box.