+ All Categories
Home > Technology > Building for Your Next Billion - Google I/O 2017

Building for Your Next Billion - Google I/O 2017

Date post: 23-Jan-2018
Category:
Upload: robert-nyman
View: 2,071 times
Download: 0 times
Share this document with a friend
109
Building for your next billion Mariya Moeva @marrrr Robert Nyman @robertnyman Tal Oppenheimer @taloppenheimer
Transcript
Page 1: Building for Your Next Billion - Google I/O 2017

Building for your next billion

Mariya Moeva@marrrr

Robert Nyman@robertnyman

Tal Oppenheimer@taloppenheimer

Page 2: Building for Your Next Billion - Google I/O 2017

Tips for building

Where our users are

Things we’ve learned

Page 3: Building for Your Next Billion - Google I/O 2017

Internet growth is happening everywhere

Page 4: Building for Your Next Billion - Google I/O 2017

2016201420152014Total internet users –

goo.gl/iJAfRJ

Page 5: Building for Your Next Billion - Google I/O 2017

20162014201520142015Total internet users –

goo.gl/iJAfRJ

Page 6: Building for Your Next Billion - Google I/O 2017

201620142015201420152016Total internet users –

goo.gl/iJAfRJ

Page 7: Building for Your Next Billion - Google I/O 2017

2014≈20142014New internet users –

goo.gl/iJAfRJ

Page 8: Building for Your Next Billion - Google I/O 2017

2014≈201420142015New internet users –

goo.gl/iJAfRJ

Page 9: Building for Your Next Billion - Google I/O 2017

2014≈2014201420152016New internet users –

goo.gl/iJAfRJ

Page 10: Building for Your Next Billion - Google I/O 2017

>100 million users came online in India last year.

goo.gl/iJAfRJ

Again.

Page 11: Building for Your Next Billion - Google I/O 2017

~1 billion Unique mobile subscribers expected in India in 2020

goo.gl/rdNZ7w

Page 12: Building for Your Next Billion - Google I/O 2017

Hundreds of millions of Chrome on Android users are from next billion user countries

Page 13: Building for Your Next Billion - Google I/O 2017

Brazil, India, Indonesia are in the top 10 countries with the highest Search volume

Page 14: Building for Your Next Billion - Google I/O 2017

What we’ve learned

Page 15: Building for Your Next Billion - Google I/O 2017

33% of smartphone users in India run out of storage space every day

goo.gl/LWchN5

Page 16: Building for Your Next Billion - Google I/O 2017

50% of users in India are on 2G

goo.gl/NVBhcf

Page 17: Building for Your Next Billion - Google I/O 2017

~$2 to download a single "Free" 40 MB app in India

goo.gl/4hIF80 goo.gl/i9JglM goo.gl/WSYY74

Page 18: Building for Your Next Billion - Google I/O 2017

Full bleed photos are greatRemove barriers

Page 19: Building for Your Next Billion - Google I/O 2017

No install Save Data Work Offlinegoo.gl/TNqxAv

Page 20: Building for Your Next Billion - Google I/O 2017

~1M app launches per day

20% decrease in bounce rate

Page 21: Building for Your Next Billion - Google I/O 2017

Optimize for speedgoo.gl/cdSKOI

Page 22: Building for Your Next Billion - Google I/O 2017

90% less data 5x faster

Page 23: Building for Your Next Billion - Google I/O 2017

50% increase in traffic due to faster loading and data sensitivity

Page 24: Building for Your Next Billion - Google I/O 2017

Full bleed photos are greatBuild for intermittent connectivity

Page 25: Building for Your Next Billion - Google I/O 2017
Page 26: Building for Your Next Billion - Google I/O 2017

Full bleed photos are greatSpeak many languagesgoo.gl/cI1OAL

Page 27: Building for Your Next Billion - Google I/O 2017

>20% of users in these countries search in two or more languages

Page 28: Building for Your Next Billion - Google I/O 2017

50% increase in Hindi searches on mobile

Page 29: Building for Your Next Billion - Google I/O 2017

Guide new users

Page 30: Building for Your Next Billion - Google I/O 2017
Page 31: Building for Your Next Billion - Google I/O 2017

Optimize speedRemove barriers

Address intermittent connectivity

Guide new users

Multilingual

Page 32: Building for Your Next Billion - Google I/O 2017

Building with this in mind

Page 33: Building for Your Next Billion - Google I/O 2017

Our best advice for catering to these challenges

Page 34: Building for Your Next Billion - Google I/O 2017

Building for everyone

Page 35: Building for Your Next Billion - Google I/O 2017

Optimize speed Address intermittent connectivity

Multilingual Guide new users

Remove barriers

Page 36: Building for Your Next Billion - Google I/O 2017

Needs the best possible reach

Automatic updates

Page 37: Building for Your Next Billion - Google I/O 2017

These constraints make it hard for native apps

Page 38: Building for Your Next Billion - Google I/O 2017

Progressive Web Apps- No install needed - Widest reach - Using least amount of data - Being kept up-to-date

Page 39: Building for Your Next Billion - Google I/O 2017

The best of native & web coming together

Page 40: Building for Your Next Billion - Google I/O 2017

Add to Homescreen Push Notifications

Offline support

Page 41: Building for Your Next Billion - Google I/O 2017

Web App Manifest

Page 42: Building for Your Next Billion - Google I/O 2017

<link rel="manifest" href="/manifest.json">

Page 43: Building for Your Next Billion - Google I/O 2017

{ "short_name": "AirHorner", "name": "Kinlan's AirHorner of Infamy", "icons": [ { "src": "launcher-icon-1x.png", "type": "image/png", "sizes": "48x48" }, { "src": "launcher-icon-4x.png", "type": "image/png", "sizes": "192x192" } ], "start_url": "index.html?utm_source=homescreen" }

Page 44: Building for Your Next Billion - Google I/O 2017

Learn more Progressive Web Apps

goo.gl/nP4U2z

Service Workers

goo.gl/U5XIUk

Add to Homescreen

goo.gl/boKhks

Push notifications

goo.gl/BsaLVS

Page 45: Building for Your Next Billion - Google I/O 2017

User experiences need to be…

Reliable Fast Engaging

Page 46: Building for Your Next Billion - Google I/O 2017

Reliable Instant loading Works offline

Fast Loads fast, stays fast

Engaging Add to homescreen Full screen Push notifications

Page 47: Building for Your Next Billion - Google I/O 2017

App size really matters

Page 48: Building for Your Next Billion - Google I/O 2017

Twitter Lite is under 1 MB

1-3% the size of Twitter native apps

goo.gl/zRUU5D

Page 49: Building for Your Next Billion - Google I/O 2017

~50% increase in pageviews

~60% increase in pages per session

Twitter Lite improvements

Page 50: Building for Your Next Billion - Google I/O 2017

60 MB on Android

100 MB on iOS

0.5 MB as a PWA

Created with Polymer Supported on all major browsers, including UC

Page 51: Building for Your Next Billion - Google I/O 2017

2x more pages visited

2x the time spent

Compared to their mobile site

Page 52: Building for Your Next Billion - Google I/O 2017

Remove barriers

Address intermittent connectivity

Multilingual Guide new users

Optimize speed

Page 53: Building for Your Next Billion - Google I/O 2017

~50KB first load

~500x lighter than on iOS

~300x lighter than on Android

Page 54: Building for Your Next Billion - Google I/O 2017

3s first load

1.8s repeat load

On 2G/ultra low 3G

Page 55: Building for Your Next Billion - Google I/O 2017

53%

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

goo.gl/4txOLB

Page 56: Building for Your Next Billion - Google I/O 2017

PWAs solve the performance on second load.

What about first load?

Page 57: Building for Your Next Billion - Google I/O 2017

Open-source initiative Make the web better, through consistently fast and high-performing pages across devices and distribution platforms

Page 58: Building for Your Next Billion - Google I/O 2017

With AMP, you're guided to only do things that are fast!

Page 59: Building for Your Next Billion - Google I/O 2017

AMP HTML AMP JS AMP Cache

Page 60: Building for Your Next Billion - Google I/O 2017

AMP HTML AMP JS AMP Cache

AMP

Page 61: Building for Your Next Billion - Google I/O 2017

Your first AMP page

Page 62: Building for Your Next Billion - Google I/O 2017

<!doctype html> <html ⚡> <head> <meta charset="utf-8"> <link rel="canonical" href="hello-world.html"> <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1"> <style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal… <script async src="https://cdn.ampproject.org/v0.js"></script> </head> <body>Hello World!</body> </html>

Page 63: Building for Your Next Billion - Google I/O 2017

Include an image

Page 64: Building for Your Next Billion - Google I/O 2017

<amp-img src="welcome.jpg" alt="Welcome" height="400" width="800">

</amp-img>

Page 65: Building for Your Next Billion - Google I/O 2017

1s load time now

4s load time previously

On slow networks

Page 66: Building for Your Next Billion - Google I/O 2017

AMP as an entry point into your PWA

AMP as a data source for your PWA

Page 67: Building for Your Next Billion - Google I/O 2017

AMP as an entry point into your PWA

goo.gl/wNdP1K

Page 68: Building for Your Next Billion - Google I/O 2017

Instant first load with AMP

Then upgrade to a PWA

Page 69: Building for Your Next Billion - Google I/O 2017

Start fast, stay fast!

Page 70: Building for Your Next Billion - Google I/O 2017

amp-install-serviceworker

goo.gl/wNdP1K

Page 71: Building for Your Next Billion - Google I/O 2017

<amp-install-serviceworker src="https://your-domain.com/sw.js" data-iframe-src="https://your-domain.com/install-sw.html" layout="nodisplay"> </amp-install-serviceworker>

Page 72: Building for Your Next Billion - Google I/O 2017

2.75s AMP load time down from 12.34s

1.63s PWA load time down from 8.77s

Tests done on Nexus 5, slow 3G

Page 73: Building for Your Next Billion - Google I/O 2017

74% visits turning into conversions

95% increase on conversions

Page 74: Building for Your Next Billion - Google I/O 2017

AMP as a data source for your PWA

goo.gl/L5RnOX

Page 75: Building for Your Next Billion - Google I/O 2017

A common scenario:

PWAs as a SPA that connects to a JSON API via Ajax

Page 76: Building for Your Next Billion - Google I/O 2017

1. Include "Shadow AMP" in your Progressive Web App

Page 77: Building for Your Next Billion - Google I/O 2017

<!-- Include a special version of AMP we call “Shadow AMP” -->

<!-- Asynchronously load the AMP-with-Shadow-DOM runtime library. --> <script async src="https://cdn.ampproject.org/shadow-v0.js"></script>

Page 78: Building for Your Next Billion - Google I/O 2017

2.Handle navigation in your Progressive Web App

Page 79: Building for Your Next Billion - Google I/O 2017

3.Use the Shadow AMP API to render a page inline

Page 80: Building for Your Next Billion - Google I/O 2017
Page 81: Building for Your Next Billion - Google I/O 2017

Network Information API goo.gl/kd5O36

Page 82: Building for Your Next Billion - Google I/O 2017

network-rtt = "Network-RTT" ":" delta-milliseconds delta-milliseconds = 1\*DIGIT

network-bw = "Network-BW" ":" kbps-value kbps-value = 1\*DIGIT

Page 83: Building for Your Next Billion - Google I/O 2017

Save-Data header goo.gl/HCsosB

Page 84: Building for Your Next Billion - Google I/O 2017

Save-Data header

Save-Data: On

Page 85: Building for Your Next Billion - Google I/O 2017
Page 86: Building for Your Next Billion - Google I/O 2017

Remove barriers

Optimize speed Multilingual Guide new users

Address intermittent connectivity

Page 87: Building for Your Next Billion - Google I/O 2017

~50%

of users in India are on 2G

goo.gl/NVBhcf

Page 88: Building for Your Next Billion - Google I/O 2017

Service Workers for handling slow or no network connection

Page 89: Building for Your Next Billion - Google I/O 2017
Page 90: Building for Your Next Billion - Google I/O 2017

Two interesting options for poor network connections and devices with slow disk access

Page 91: Building for Your Next Billion - Google I/O 2017

1. Timeouts for slow networks, then fallback to device storage

Page 92: Building for Your Next Billion - Google I/O 2017

2. Race conditions for devices with slow read access

Page 93: Building for Your Next Billion - Google I/O 2017

~2/3

of users in Nigeria are on 2G

goo.gl/Qxc9jz

Page 94: Building for Your Next Billion - Google I/O 2017

92% less data for first load vs. native

82% less data for first transaction vs. native

goo.gl/Qxc9jz

Page 95: Building for Your Next Billion - Google I/O 2017

63% less data for first load vs. previous web

84% less data for first transaction vs. previous web

goo.gl/Qxc9jz

Page 96: Building for Your Next Billion - Google I/O 2017

Remove barriers

Optimize speed Address intermittent connectivity

Guide new users

Multilingual

Page 97: Building for Your Next Billion - Google I/O 2017
Page 98: Building for Your Next Billion - Google I/O 2017
Page 99: Building for Your Next Billion - Google I/O 2017
Page 100: Building for Your Next Billion - Google I/O 2017

Remove barriers

Optimize speed Address intermittent connectivity

Multilingual Guide new users

Page 101: Building for Your Next Billion - Google I/O 2017

Making sure to help users when they visit your web site

Page 102: Building for Your Next Billion - Google I/O 2017

Add to Homescreen

Page 103: Building for Your Next Billion - Google I/O 2017

5-6x more likely users will use Add to Homescreen than install the equivalent native app

Page 104: Building for Your Next Billion - Google I/O 2017

63% of users are on 2G

Fast user experience essential goo.gl/Qxc9jz

Page 105: Building for Your Next Billion - Google I/O 2017

60% of all visits from the homescreen icon

goo.gl/Qxc9jz

70%

higher conversion than average users

Page 106: Building for Your Next Billion - Google I/O 2017

Optimize speedRemove barriers

Address intermittent connectivity

Guide new users

Multilingual

Progressive Web Apps

Page 107: Building for Your Next Billion - Google I/O 2017

Build for your next billion

Page 108: Building for Your Next Billion - Google I/O 2017

How to get started

developers.google.com/web/billions/

Page 109: Building for Your Next Billion - Google I/O 2017

Thank you!Mariya Moeva@marrrr

Robert Nyman@robertnyman

Tal Oppenheimer@taloppenheimer


Recommended