A year with progressive web apps! #webinale

Slide 1

Slide 1 text

A year with progressive web apps! Antonio Perić-Mažar, Locastic 06.04.2019., #webinale

Slide 2

Slide 2 text

Antonio Perić-Mažar CEO @ Locastic Co-Founder @ Tinel Meetup Co-Founder @ Blockada [email protected] @antonioperic

Slide 3

Slide 3 text

Locastic • We help clients create amazing web and mobile apps (since 2011) • mobile development • web development • UX/UI • Training and Consulting • Shift Conference, Symfony Croatia • www.locastic.com t: @locastic

Slide 4

Slide 4 text

Stop call progressive web apps trendy!

Slide 5

Slide 5 text

Our world today

Slide 6

Slide 6 text

MOBILE

Slide 7

Slide 7 text

Slide 8

Slide 8 text

MOBILE.UX.

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

https://www.morevisibility.com/blogs/analytics/setting-up-and-reporting-on-site-speed-in-google-analytics.html October 2016

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

Mobile web (UX) is broken!!!

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

And trust me… you will never had enough cheese

Slide 17

Slide 17 text

“I don't care how many kick-ass Visio architecture diagrams you have; as far as the user is concerned, the UI is the application. I know UI US HARD, but you have to build an impressive UI if you want to be taken seriously. Give your UI the high priority it deserves.” Jeﬀ Atwood, Coding Horror blog

Slide 18

Slide 18 text

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

Capebility Reach

Slide 21

Slide 21 text

“A Progressive Web App uses modern web capabilities to deliver an app-like user experience.”

Slide 22

Slide 22 text

“A Progressive Web App uses modern web capabilities to deliver an app-like user experience.”

Slide 23

Slide 23 text

PWA is: • Progressive - Works for every user, regardless of browser choice because it's built with progressive enhancement as a core tenet. • Responsive - Fits any form factor: desktop, mobile, tablet, or whatever is next. • Connectivity independent - Enhanced with service workers to work oﬀline or on low-quality networks. • App-like - Feels like an app, because the app shell model separates the application functionality from application content . • Fresh - Always up-to-date thanks to the service worker update process.

Slide 24

Slide 24 text

PWA is: • Safe - Served via HTTPS to prevent snooping and to ensure content hasn't been tampered with. • Discoverable - Is identifiable as an "application" thanks to W3C manifest and service worker registration scope, allowing search engines to find it. • Re-engageable - Makes re-engagement easy through features like push notifications. • Installable - Allows users to add apps they find most useful to their home screen without the hassle of an app store. • Linkable - Easily share the application via URL, does not require complex installation.

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

Fast Integrated Reliable Engaging 4 things to focus on

Slide 27

Slide 27 text

Fast Integrated Reliable Engaging

Slide 28

Slide 28 text

Fast • No junky scrolling • No slow load performance • Measure and improve all the time • Bad connection (or no connection) is not excuse

Slide 29

Slide 29 text

53% of users abandon sites that take longer than 3 seconds to load

Slide 30

Slide 30 text

https://cloudfour.com/thinks/ios-doesnt-support-progressive-web-apps-so-what/

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

App shell model • Reliable performance that is consistently fast • Native-like interactions • Economical use of data

Slide 33

Slide 33 text

Fast Integrated Reliable Engaging

Slide 34

Slide 34 text

Integrated • User should not reach browser to reach your app • They should be able to interact same as with any other app on their device • They expect to have all possibilities as other apps • Users should be able to start app from their home screen

Slide 35

Slide 35 text

https://www.mobigyaan.com/android-8-0-oreo-vs-ios-11-which-is-better

Slide 36

Slide 36 text

https://techcrunch.com/2017/08/25/majority-of-u-s-consumers-still-download-zero-apps-per-month-says-comscore/

Slide 37

Slide 37 text

https://techcrunch.com/2017/08/25/majority-of-u-s-consumers-still-download-zero-apps-per-month-says-comscore/

Slide 38

Slide 38 text

https://www.technology.org/2017/07/28/progressive-web-apps-vs-native-which-is-better-for-your-business/

Slide 39

Slide 39 text

80% users intentionally moved apps to their home screen

Slide 40

Slide 40 text

Broken experience • Required user interaction • Where it will start? • Would it work oﬀline? https://medium.com/@saigeleslie/how-to-create-a-progressive-web-app-with-react-in-5-mins-or-less-3aae3fe98902

Slide 41

Slide 41 text

Web manifest • Simple JSON file • Tell browsers about your app and how it should behave once app is ‘installed’ • Having manifest is required to show add to home screen pop-up • Works for desktop and mobile apps (chrome) • https://manifest-validator.appspot.com/ • https://app-manifest.firebaseapp.com/

Slide 42

Slide 42 text

{ "background_color":"#ffffff", "display":"standalone", "icons":[ … ], "name":"Twitter", "short_name":"Twitter", "start_url":"/", "theme_color":"#ffffff", “scope":"/" } You can add it now to   your app

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

https://ponyfoo.com/articles/progressive-app-serviceworker

Slide 45

Slide 45 text

40% higher interaction rate from Home screen

Slide 46

Slide 46 text

Web Payment API!

Slide 47

Slide 47 text

66% of purchases on mobile are on the mobile web

Slide 48

Slide 48 text

1/3 of purchases on Web are via mobile That means the UX   is BROKEN!

Slide 49

Slide 49 text

Checkout forms today: • Manual • Tedious • Slow • N-taps http://www.alyssatucker.com/improving-hollars-ios-checkout-process/

Slide 50

Slide 50 text

Autofill - step forward • Autocomplete attributes • 30% faster • Automatic • Simple • Slow • n-taps http://www.alyssatucker.com/improving-hollars-ios-checkout-process/

Slide 51

Slide 51 text

Web Payment API!

Slide 52

Slide 52 text

No content

Slide 53

Slide 53 text

No content

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

Web Payment API! • Automatic • Simple • Fast • 1-tap • Supportes payment gatway,  or some applications payment   (Google Pay) https://paymentrequest.show/images/pr-woocommerce.gif

Slide 56

Slide 56 text

More APIs • Media Session • Media Capture API • Casting support • Web bluetooth • Web Share

Slide 57

Slide 57 text

More APIs • Media Session • Media Capture API • Casting support • Web bluetooth • Web Share

Slide 58

Slide 58 text

Remember users expect to be able to interact with your app in the same way that they do all of the other apps on their device

Slide 59

Slide 59 text

Fast Integrated Reliable Engaging

Slide 60

Slide 60 text

Reliable Reliability means, never showing the Downsaur

Slide 61

Slide 61 text

No content

Slide 62

Slide 62 text

Reliable • The quality of a network connection can be aﬀected by a number of factors such as: • Poor coverage of a provider. • Extreme weather conditions. • Power outages. • Users travelling into “dead zones” such as buildings that block their network connections. • Travelling on a train and going through a tunnel. • Internet connection is managed by a third party and time boxed when it will be active or inactive like in an airport or hotel. • Cultural practises that require limited or no internet access at specific times or days.

Slide 63

Slide 63 text

Reliable • We need instant loading oﬀline • 60% of mobile connection is 2G • Fast Application is UX • 14 sec to load average website on 4g • 19 sec to load average website on 3G

Slide 64

Slide 64 text

Service Workers

Slide 65

Slide 65 text

Service Workers

Slide 66

Slide 66 text

Service Workers Service Workers

Slide 67

Slide 67 text

Service Workers • Rich oﬀline experiences • Background syncs • Push notifications • …

Slide 68

Slide 68 text

Service Workers • Script that browser runs in background, separated from web page • It is Javascript worker, so it cannot access to DOM directly • Service worker is a programmable network proxy, allowing you to control how network requests from your page are handled.

Slide 69

Slide 69 text

Service Workers • It's terminated when not in use, and restarted when it's next needed, so you cannot rely on global state within a service worker's onfetch and onmessage handlers. • Service workers make extensive use of promises • Service worker is for second load

Slide 70

Slide 70 text

Service Workers lifecycle

Slide 71

Slide 71 text

Register a Service Worker if ('serviceWorker' in navigator) { window.addEventListener('load', function() { navigator.serviceWorker.register('/sw.js').then(function(registration) { // Registration was successful console.log('ServiceWorker registration successful with scope: ', registration.scope); }, function(err) { // registration failed :( console.log('ServiceWorker registration failed: ', err); }); }); }

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

Service workers Events • On install - as a dependency • On install - not as a dependency • On activate • On user interaction • On network response • Stale-while-revalidate • On push message • On background-sync

Slide 74

Slide 74 text

On install - as a dependency

Slide 75

Slide 75 text

On install - as a dependency self.addEventListener('install', function(event) { event.waitUntil( caches.open('mysite-static-v3').then(function(cache) { return cache.addAll([ '/css/whatever-v3.css', '/css/imgs/sprites-v6.png', '/css/fonts/whatever-v8.woff', '/js/all-min-v4.js' // etc ]); }) ); });

Slide 76

Slide 76 text

On install - not as a dependency

Slide 77

Slide 77 text

Update Service Worker • Update your service worker JavaScript file. When the user navigates to your site, the browser tries to redownload the script file that defined the service worker in the background. If there is even a byte's diﬀerence in the service worker file compared to what it currently has, it considers it new. • Your new service worker will be started and the install event will be fired. • At this point the old service worker is still controlling the current pages so the new service worker will enter a waiting state. • When the currently open pages of your site are closed, the old service worker will be killed and the new service worker will take control. • Once your new service worker takes control, its activate event will be fired.

Slide 78

Slide 78 text

On activate

Slide 79

Slide 79 text

Update Service Worker • self.skipWaiting() • Skips waiting for refresh to start using new SW

Slide 80

Slide 80 text

On User Interaction

Slide 81

Slide 81 text

On Network response

Slide 82

Slide 82 text

State-while-revalidate

Slide 83

Slide 83 text

On Background Sync

Slide 84

Slide 84 text

SW: Serving suggestions - responding to requests • Cache only • Network only • Cache, falling back to network • Cache & network race • Network falling back to cache • Cache then network • Generic fallback

Slide 85

Slide 85 text

Cache only

Slide 86

Slide 86 text

Network only

Slide 87

Slide 87 text

Cache, falling back to network

Slide 88

Slide 88 text

Cache & network race

Slide 89

Slide 89 text

Network, falling back to Cache

Slide 90

Slide 90 text

Cache, than Network

Slide 91

Slide 91 text

Generic fallback

Slide 92

Slide 92 text

No content

Slide 93

Slide 93 text

No content

Slide 94

Slide 94 text

No content

Slide 95

Slide 95 text

Reliable conclusion • Think how you design for the success, failure and instability of a network connection • Data may be expensive, so be considerate to the user • Make sure performance is part of your design process and UX • Try to provide oﬀline by default if your app doesn't require much data • Inform users of their current state and of changes in states • https://serviceworke.rs/ - diﬀerent examples

Slide 96

Slide 96 text

https://serviceworke.rs/ - diﬀerent examples

Slide 97

Slide 97 text

Your goal is to provide a good experience that lessens the impact of changes in connectivity

Slide 98

Slide 98 text

Fast Integrated Reliable Engaging

Slide 99

Slide 99 text

Engaging • Charming and Attractive • Shift way how we think in patterns and designs from web patterns to some native patterns • Push notifications (browser doesn’t need to be opened) • Push Notification API

Slide 100

Slide 100 text

Engaging

Slide 101

Slide 101 text

What makes good notification Push. Push. Back upon now. (Courtesy Enrique Iglesias)

Slide 102

Slide 102 text

What makes good notification • Timely - I feel I need and it matters now • Precise - specific info, what happens • Personal - make it personal

Slide 103

Slide 103 text

What makes good notification

Slide 104

Slide 104 text

https://www.slideshare.net/SeulgiChoi4/pwa-push-notiﬁcation

Slide 105

Slide 105 text

https://www.slideshare.net/SeulgiChoi4/pwa-push-notiﬁcation

Slide 106

Slide 106 text

No content

Slide 107

Slide 107 text

Push Notifications { "body": "Did you make a $1,000,000 purchase at Dr. Evil...", "icon": "images/ccard.png", "vibrate": [200, 100, 200, 100, 200, 100, 400], "tag": "request", "actions": [ { "action": "yes", "title": "Yes", "icon": "images/yes.png" }, { "action": "no", "title": "No", "icon": "images/no.png" } ] }

Slide 108

Slide 108 text

43% agrees to an app’s request to allow push notifications

Slide 109

Slide 109 text

No content

Slide 110

Slide 110 text

Tools!

Slide 111

Slide 111 text

Lighthouse

Slide 112

Slide 112 text

No content

Slide 113

Slide 113 text

http://mobilehtml5.org/ http://mobilehtml5.org/ts/ http://mobilehtml5.org/tests/ http://mobilehtml5.org/tests/ te http://mobilehtml5.org/tests/ t http://mobilehtml5.org/tests/

Slide 114

Slide 114 text

Some show case!

Slide 115

Slide 115 text

65% increase in page per session 75% increase in Tweets sent  20% decrease in bounce rate Twitter Lite

Slide 116

Slide 116 text

76% higher conversation across browsers 4x higher interaction rate from Add to screen Increased usage of native apps also Alibaba

Slide 117

Slide 117 text

80%+ conversation 54% smaller than Android app 120% smaller than iOS app BookMyShow

Slide 118

Slide 118 text

Cut load times from 11.91 to 4.69 seconds 90% smaller than Native Android App https://medium.com/@addyosmani/a-tinder-progressive-web-app-performance- case-study-78919d98ece0 Tinder