Slide 1

Slide 1 text

Web &
 Mobile @jcemer

Slide 2

Slide 2 text

I work on GloboPlay.
 globo.com

Slide 3

Slide 3 text

This talk is about two important subjects and their intersection.

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

Mobile devices are dominating the Internet.

Slide 7

Slide 7 text

Companies should focus on a mobile- first approach 
 for their websites.

Slide 8

Slide 8 text

https://speakerdeck.com/jcemer/

Slide 9

Slide 9 text

1. Mobile Web versions

Slide 10

Slide 10 text

Facebook and Google are trying to filter and classify the Web.

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

Instant Articles are a new way for any publisher to create fast, interactive articles on Facebook.

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

The average load time was between 
 0 and 300 ms, compared with 
 3.66 seconds for similar web articles.

Slide 19

Slide 19 text

No ads can appear above the fold. This would help with rapid initial loading.

Slide 20

Slide 20 text

The biggest mistake we’ve made as a company is betting on HTML5 over native. @Zuckerberg, 2012

Slide 21

Slide 21 text

The key to Instant Articles' functionality is the strictly formatted HTML5 which is optimized for faster loading.

Slide 22

Slide 22 text

https://developers.facebook.com/
 docs/instant-articles/reference/

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

37% + reach 22% + shares 83% + Likes 57% + link clicks. https://blog.hootsuite.com/started-using-facebook- instant-articles/

Slide 25

Slide 25 text

As with any publishing platform, the value of Instant Articles greatly depends on your business model 
 and goals. https://blog.bufferapp.com/facebook-instant-articles

Slide 26

Slide 26 text

Users won't have to click out of Facebook to view an article.

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

AMP-HTML is simply HTML5 with a set of specifications (requirements and restrictions).

Slide 33

Slide 33 text

https://github.com/ampproject/amphtml

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

The big players are trying to restrict 
 and split the Web.

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

AMP and Instant Articles create different versions of a same website.

Slide 38

Slide 38 text

2. Mobile Apps

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

No-one is going to install an app for each service, your mobile Web experience has to be good.

Slide 42

Slide 42 text

No content

Slide 43

Slide 43 text

Deepest engagement for the longest period of time happens in Apps, so Apps matter. http://venturebeat.com/2015/09/25/wait-what-mobile-browser- traffic-is-2x-bigger-than-app-traffic-and-growing-faster/

Slide 44

Slide 44 text

Native apps 
 might survive.

Slide 45

Slide 45 text

Progressive Web Apps

Slide 46

Slide 46 text

Progressive Web Apps have the reach of the web, and are reliable, fast and engaging.

Slide 47

Slide 47 text

https:// dev.opera.com/

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

1. Deliver a Mobile-friendly design™

Slide 50

Slide 50 text

No content

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

Slide 53

Slide 53 text

@media screen and (max-width: 1000px) { 
 /* Styles */ 
 } @media screen and (max-width: 560px) { 
 /* Styles */ 
 }

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

Designing in the browser allows the designer to keep checking the results in different devices.

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

16:1 3:4 2:3

Slide 58

Slide 58 text

No content

Slide 59

Slide 59 text

2. Apply progressive enhance

Slide 60

Slide 60 text

The app should works for every user, regardless of browser choice.

Slide 61

Slide 61 text

Responsive Design != one size fits all. @Brad Frost

Slide 62

Slide 62 text

Don’t get hung up thinking that media queries are the only tool in your toolbox. @Brad Frost

Slide 63

Slide 63 text

I work for Booking.com, and we support IE 7, and I use flexbox. @Zoe Mickley

Slide 64

Slide 64 text

Start with the content and then enhance the experience.

Slide 65

Slide 65 text

Modernizr tells you what HTML, CSS and JavaScript features the user’s browser has to offer. https://modernizr.com/

Slide 66

Slide 66 text

No content

Slide 67

Slide 67 text

@Brad Frost

Slide 68

Slide 68 text

3. Ensure fast page load performance

Slide 69

Slide 69 text

0.1 second reacting instantaneously. @Jakob Nielsen, 1993

Slide 70

Slide 70 text

1 second
 user will notice the delay.

Slide 71

Slide 71 text

10 seconds
 users will want to perform other tasks while waiting.

Slide 72

Slide 72 text

Source:
 Forrester Consulting 
 http://bit.ly/1ttKspI

Slide 73

Slide 73 text

No content

Slide 74

Slide 74 text

https://developers.google.com/ speed/pagespeed/insights/

Slide 75

Slide 75 text

No content

Slide 76

Slide 76 text

https:// webpagetest.org/

Slide 77

Slide 77 text

4. Use a secure network connection

Slide 78

Slide 78 text

HTTPS ensures that the contents of communications between the user and site cannot be read or forged.

Slide 79

Slide 79 text

No content

Slide 80

Slide 80 text

The page that's making the Geolocation API call must be served from a secure context.

Slide 81

Slide 81 text

https:// letsencrypt.org/

Slide 82

Slide 82 text

5. Create a manifest.json

Slide 83

Slide 83 text

Manifest enable 
 add to homescreen and a launch experience more comparable to native apps.

Slide 84

Slide 84 text

No content

Slide 85

Slide 85 text

No content

Slide 86

Slide 86 text

No content

Slide 87

Slide 87 text

No content

Slide 88

Slide 88 text

https://www.w3.org/TR/appmanifest/

Slide 89

Slide 89 text

No content

Slide 90

Slide 90 text

6. Allow the app to be loaded on offline/flaky connections

Slide 91

Slide 91 text

No content

Slide 92

Slide 92 text

Service workers allow good caching strategies.

Slide 93

Slide 93 text

Source: https://auth0.com/blog/creating-offline-first-
 web-apps-with-service-workers/

Slide 94

Slide 94 text

https:// googlechrome.github.io/ samples/service-worker/ custom-offline-page/

Slide 95

Slide 95 text

http://www.slideshare.net/caelumdev/ serviceworkers-sergio

Slide 96

Slide 96 text

No content

Slide 97

Slide 97 text

PWAs can also benefit from 
 push notifications, 
 like native apps.

Slide 98

Slide 98 text

No content

Slide 99

Slide 99 text

No content

Slide 100

Slide 100 text

https:// pwa.rocks/

Slide 101

Slide 101 text

PWAs are in equal parts new Web APIs, design patterns, and marketing fluff.

Slide 102

Slide 102 text

The Web still matter…

Slide 103

Slide 103 text

Thank you! @jcemer