Slide 1

Slide 1 text

The Case for Progressive Web Apps

Slide 2

Slide 2 text

We need a progressive web app!

Slide 3

Slide 3 text

What is a progressive web app?

Slide 4

Slide 4 text

How do we create a plan for this?

Slide 5

Slide 5 text

Do we need a progressive web app?

Slide 6

Slide 6 text

How does the CEO even know about progressive web apps?

Slide 7

Slide 7 text

Cool. I’ve been wanting to play with service workers… Maybe we can use Vue.js here as well… I wonder if this can be used as excuse to switch to node js…

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

How does the CEO even know about progressive web apps?

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

eXtra Electronics • 12% click-through rate • 100% more sales from users arriving via web push • 4x increase in re-engagement Source: Google, http://bit.ly/2eqSf18

Slide 13

Slide 13 text

Source: https://medium.com/dev-channel/a-pinterest-progressive-web-app-performance-case-study-3bd6ed2e6154

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

What is a progressive web app?

Slide 16

Slide 16 text

Original Definition by Frances Berriman and Alex Russell Responsive 
 Fit any form factor. RWD FTW! Connectivity Independent
 Offline features thanks to service workers. App-like interactions
 App shell for apps navigation. Fresh
 Up-to-date thanks to service workers. Safe
 Served on HTTPS. Discoverable
 Manifest files identify them as apps. Re-engageable
 Push notifications bring people back to apps. Installable
 Can be installed to the home screen w/o app stores. Linkable
 Still part of the web—URLs still work. Progressive
 Use progressive enhancement for better experience.

Slide 17

Slide 17 text

Source: FlipKart, http://bit.ly/2ejW2Rr Flipkart’s Progressive Web App

Slide 18

Slide 18 text

Source: https://blog.twitter.com/ 2017/how-we-built-twitter-lite Twitter Lite Twitter Lite is interactive in less than 5 seconds over 3G on most devices, with average load times reduced by over 30%.

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

https://docs.google.com/presentation/d/14fBthXt3i3nRbi7vUrVXj3CjI1ILcYlKDAUMf1LXWpY/edit#slide=id.p22

Slide 27

Slide 27 text

PWA is a website that has been enhanced with: {manifest} https service worker Credit to Jeremy Keith for explicitly declaring a technical definition: https://adactio.com/journal/13098

Slide 28

Slide 28 text

Progressive web apps allow us to build experiences that previously required a native application.

Slide 29

Slide 29 text

https://www.youtube.com/watch?v=3tb-1MWg44Y

Slide 30

Slide 30 text

The hype can be a turn off https://twitter.com/elliotecweb/status/864070806569066497

Slide 31

Slide 31 text

The name isn’t for you and worrying about it is distraction from just building things that work better for everyone. The name is for your boss, for your investor, for your marketeer. —Frances Berriman, Naming Progressive Web Apps

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

Do we need a progressive web app?

Slide 34

Slide 34 text

If so, you would probably benefit from a PWA. Does your organization have a website?

Slide 35

Slide 35 text

Does your organization make money on your website via e-commerce, advertising, or some other method? If so, you definitely need a progressive web app.

Slide 36

Slide 36 text

Progressive Web Apps Simply Make Sense (Irrespective of what you do on native)

Slide 37

Slide 37 text

1. Not every customer or potential customer will install your native app.

Slide 38

Slide 38 text

DUH!

Slide 39

Slide 39 text

Sometimes we need to restate the obvious.

Slide 40

Slide 40 text

Plus, there are cracks in the app store.

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

No content

Slide 43

Slide 43 text

Over 2 million apps available in iOS and Android app stores. Source: Statista, http://bit.ly/2fleesH | Photo by Blake Patterson, http://bit.ly/2foGNpj

Slide 44

Slide 44 text

8+ apps 5-7 apps 4 apps 3 apps 2 apps 1 app 0 apps 49% 13% 11% 8% 6% 7% 6% U.S. smartphone users’ number of apps downloads per month Source: Comscore 2016 U.S. Mobile App Report, http://bit.ly/2d27iPI

Slide 45

Slide 45 text

Average Android App Retention of Daily Active Users Source: Quettra via Andrew Chen http://bit.ly/1Hq53AR Percentage of Users Still Active 0% 25% 50% 75% 100% Days Since App Install 0 1 3 7 14 30 60 90

Slide 46

Slide 46 text

No content

Slide 47

Slide 47 text

© comScore, Inc. Proprietary. 26 Advertising and marketing is becoming a more important driver of app installs, while the app store’s influence may have peaked. App acquisition appears to be moving from ‘pull’ to ‘push’. App stores remain the most important method, but they are no longer growing in importance. Meanwhile, more users are now discovering apps from websites, digital ads and traditional media ads, highlighting the increasing importance of traditional push marketing for user acquisition. Most Common App Discovery Channels Among Smartphone Users Source: comScore MobiLens, U.S., Age 13+, 3 Month Average Ending June 2016 vs. June 2015 21% 14% 16% 9% 8% 9% 8% 6% 21% 14% 16% 11% 8% 11% 9% 9% 0% 5% 10% 15% 20% 25% Searched app store Featured/ Top List in app store via friend/ family via comment/ review/ social site via news/ print review/ TV show via a website via Ad on device browser/ app via Ad on TV/ print/ billboard % of Smartphone Users Jun-2015 Jun-2016 App Store Word-of-Mouth/Opinion Advertising/Marketing Being in the app store is no longer enough. Cost of acquisition higher.

Slide 48

Slide 48 text

© comScore, Inc. Proprietary. 15 And mobile audience growth is being driven more by mobile web properties, which are actually bigger and growing faster than apps. A comparison of the Top 1000 Apps vs. the Top 1000 Mobile Web Properties shows that despite apps dominance in usage time, mobile web is responsible for big audiences on mobile. Mobile web audiences are almost 3x the size and growing 2x as fast as app audiences. Average Monthly Audience: Top 1000 Mobile Apps vs. Top 1000 Mobile Web Properties Source: comScore Mobile Metrix, U.S., Age 18+ - 2,000 4,000 6,000 8,000 10,000 12,000 Jun-2014 Sep-2014 Dec-2014 Mar-2015 Jun-2015 Sep-2015 Dec-2015 Mar-2016 Jun-2016 Unique Visitors (000) Apps Mobile Web +82% vs. 2014 +45% vs. 2014 “Mobile web audiences are almost 3x the size and growing 2x as fast as app audiences.”

Slide 49

Slide 49 text

2. You should provide a secure site or app for your web customers

Slide 50

Slide 50 text

Image by CHRISTOPHER DOMBRES, http://bit.ly/2fKjJoC

Slide 51

Slide 51 text

Photo by Mario Antonio Pena Zapatería, http://bit.ly/2fuQ27D

Slide 52

Slide 52 text

Let’s Encrypt is a free, automated, and open Certificate Authority. We are a 501(c)(3) nonprofit. We're running a crowdfunding campaign to support our operations, please consider contributing now! Get Started Donate FROM OUR BLOG Nov 1, 2016 Launching Our Crowdfunding Campaign Today we kicked off our first crowdfunding campaign with the goal of raising enough funds to cover about one month of our operations - $200,000. Read more Oct 27, 2016 Our First Grant: The Ford Foundation We are proud to announce that The Ford Foundation has awarded us a grant to help our growing operations. Read more Oct 24, 2016 Squarespace OCSP Stapling Implementation MA JOR SPONSORS Documentation Get Help Donate ▾ About Us ▾

Slide 53

Slide 53 text

Not part of PWAs, but big speed boost only possible with HTTPS.

Slide 54

Slide 54 text

3. You should provide a fast experience for your web customers

Slide 55

Slide 55 text

The Washington Post PWA shows big speed increase

Slide 56

Slide 56 text

The Washington Post PWA shows big speed increase

Slide 57

Slide 57 text

Service workers key to performance boon Source: Google, http://bit.ly/2fpGrRr

Slide 58

Slide 58 text

4. Your web customers would benefit from an offline experience

Slide 59

Slide 59 text

Service workers are also key to providing an offline experience

Slide 60

Slide 60 text

5. Your web customers might benefit from push notifications

Slide 61

Slide 61 text

Push notifications can help increase engagement

Slide 62

Slide 62 text

6. You can create a text file and some icons for a Web Manifest

Slide 63

Slide 63 text

Manifest files are simple JSON documents

Slide 64

Slide 64 text

{ name: "Cloud Four", short_name: "Cloud Four", description: "We design and develop responsive websites and progressive web apps.", icons: [ { src: "/android-chrome-192x192.png", sizes: "192x192", type: "image/png" }, { src: "/android-chrome-512x512.png", sizes: "512x512", type: "image/png" } ], theme_color: "#456BD9", background_color: "#FFFFFF", display: "standalone", orientation: "natural", start_url: "/", gcm_sender_id: "482941778795" } Manifest files are simple JSON documents

Slide 65

Slide 65 text

Every step on the path to a PWA makes sense on its own.

Slide 66

Slide 66 text

FUD Fear, Uncertainty, Doubt

Slide 67

Slide 67 text

We already have a native app, why do we need a PWA?

Slide 68

Slide 68 text

Reach people who don’t have your native app installed or are on a different device.

Slide 69

Slide 69 text

Your website is often a customer’s first interaction with your company. 
 A better web experience will likely mean more revenue and more native app installs.

Slide 70

Slide 70 text

The web can’t do [insert thing here]

Slide 71

Slide 71 text

No content

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

No content

Slide 74

Slide 74 text

No content

Slide 75

Slide 75 text

No content

Slide 76

Slide 76 text

No content

Slide 77

Slide 77 text

No content

Slide 78

Slide 78 text

No content

Slide 79

Slide 79 text

No content

Slide 80

Slide 80 text

No content

Slide 81

Slide 81 text

No content

Slide 82

Slide 82 text

No content

Slide 83

Slide 83 text

No content

Slide 84

Slide 84 text

https://www.flickr.com/photos/ashleyrosex/2861690380 The web can do more than we think.

Slide 85

Slide 85 text

But iOS doesn’t support PWAs…

Slide 86

Slide 86 text

No content

Slide 87

Slide 87 text

PWAs work fine on older browers. They are progressive.

Slide 88

Slide 88 text

AliExpress • 104% for new users across all browsers in conversion • 82% increase in iOS conversion Source: Google, http://bit.ly/2fq2ckc

Slide 89

Slide 89 text

Wego • 50% increase in iOS conversion • 35% increase in average iOS session duration Source: Google, https://bit.ly/2uOsoNM

Slide 90

Slide 90 text

The Washington Post saw 5x increase in user engagement

Slide 91

Slide 91 text

Why? Performance. PWA faster even without SW.

Slide 92

Slide 92 text

PWAs are a trojan horse for performance.

Slide 93

Slide 93 text

https://developers.google.com/web/showcase/2017/wego

Slide 94

Slide 94 text

How do we create a plan for this?

Slide 95

Slide 95 text

Progressively Punny

Slide 96

Slide 96 text

PWAs are progressive because… They are built on Progressive Enhancement

Slide 97

Slide 97 text

PWAs are progressive because… They promote a progressive relationship with your users First page • Page loads fast normally • Service worker installs after core content • Service worker pre-fetches assets • Assets explicitly cached Second page • Page loads even faster because of cache • App shell loading pattern? User indicates interest • Check to see if browser supports push • Ask if user wants notifications • If yes, ask browser for permission. User responds to notification • We can provide an improved experience Browser detects engagement • Asks user if they want to add to home screen • Now app may have better experience

Slide 98

Slide 98 text

PWAs are progressive because… Progressive Roadmap {manifest} https Jul 13 Redesign launches Better security with HTTPS Faster site via HTTP/2 Better bookmarks via manifest Oct 3 Faster pages Offline fallback It’s a PWA! service worker Oct 18 Offline pages Offline indicator Improved font loading Nov 22 Push notifications HTTP/2 Link Preload Dec 7 Small tweaks PWA announced

Slide 99

Slide 99 text

Progressive Web App Blueprint Planning & Definition

Slide 100

Slide 100 text

Define Your Ideal Progressive Web App

Slide 101

Slide 101 text

Offline Interactivity Cache for Perf Only Offline Native App Stores Website with Perf Improvements Full Screen, App Shell New APIs No Add to Home Screen Basic PWA Feels Like An App Installation and Discovery No Push Notifications Personalized and Integrated Push Push Notifications Beyond PWAs

Slide 102

Slide 102 text

Benchmark & Plan to Measure

Slide 103

Slide 103 text

Progressive Web App Blueprint Planning & Definition Technical Debt (if Necessary) Gather team Brainstorm Ideal PWA Benchmarks and measurement plans Build roadmap

Slide 104

Slide 104 text

Assess Current Website

Slide 105

Slide 105 text

Is Your Website Reasonably Fast?

Slide 106

Slide 106 text

Is it Usable?

Slide 107

Slide 107 text

Progressive Web App Blueprint Planning & Definition Technical Debt (if Necessary) Baseline PWA Front-end Additions Larger Initiatives Gather team Brainstorm Ideal PWA Benchmarks and measurement plans Build roadmap Assess current website Fix performance issues Fix usability issues Manifest HTTPS Service worker for performance Offline Fallback Cache recently viewed pages Precache popular or important pages Add third-party push notification service CMS plugin for push notifications Payment Request API Credentials Management API Integrate notifications with backend systems Background sync Move to app shell

Slide 108

Slide 108 text

Baseline PWA Front-end Additions Larger Initiatives Progressive Web App Blueprint Planning & Definition Technical Debt (if Necessary) Gather team Brainstorm Ideal PWA Benchmarks and measurement plans Build roadmap Assess current website Fix performance issues Fix usability issues Manifest HTTPS Service worker for performance Offline Fallback Cache recently viewed pages Precache popular or important pages Add third-party push notification service CMS plugin for push notifications Payment Request API Credentials Management API Integrate notifications with backend systems Background sync Move to app shell

Slide 109

Slide 109 text

Every step on the path to a PWA makes sense on its own.

Slide 110

Slide 110 text

No content

Slide 111

Slide 111 text

More in the book! Available now. Follow @abookapart or @thepwabook for updates. https://abookapart.com/products/ progressive-web-apps No 28 PROGRESSIVE WEB APPS Jason Grigsby

Slide 112

Slide 112 text

Thank You!

Slide 113

Slide 113 text

Thank You! White Blank Notebook by Tirachard Kumtanom Woman Executive Holding Tablet by Pixabay Schedule Planning by Startup Stock Photos Hackers by Christopher Dombres NSA by by Mario Antonio Pena Zapatería Map Location Symbol by Tumisa Smartphone on Bridge by Jeremy Levin Hype by Kerry J Instagram App on iPhone by Pixabay Man in Fuzzy Hat by Gratisography Southbank - Samsung Galaxy S8 (1) by TaylorHerring Now THIS is comfort! by Garry Wilmore Trojan Horse by Hsing Wei Cold Snow Man Person Asphalt Blur Car City by Pixabay Woman Listening to Music by bruce mars Woman and Dog by Tookapic Focus by Mark Hunter Person Holding Silver iPhone by rawpixel.com MacBook Air Beside Painting by rawpixel.com Android Phone by freestocks.org Smart Watch by Oliur Rahman Apple Office Internet iPad by Pixabay Woman Jumping by Quang Anh Ha Nguyen SEM by Pixabay Legs on Chair by kaboompics.com In Hiding by Taylor McBride Medusa Kill Switch by Scott Hart White Auto Gauge by Mikes Photos Blue and Silver Stethoscope by Pixabay Tortoise by Frans Van Heerden iPhone Photo on Railroad Tracks by Kaique Rocha database by ✦ Shmidt Sergey ✦ from the Noun Project Cloud by Blackwoodmedia.com.au from the Noun Project Responsive Design by Delwar Hossain from the Noun Project cogs by Gregor Cresnar from the Noun Project Special thanks to these fabulous people who graciously shared their work under Creative Commons.