Gaining Control in the Great Unknown - The state of mobile browsers and how to handle them

Slide 1

Slide 1 text

GAINING CONTROL IN THE GREAT UNKNOWN Drupalcamp - November 2013

Slide 2

Slide 2 text

Griass Enk

Slide 3

Slide 3 text

@ddprrt

Slide 4

Slide 4 text

Netural

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

Lafers grill recipes The need precise control I need to put meat on fire

Slide 7

Slide 7 text

Weber-Kit

Slide 8

Slide 8 text

Controlled Environments

Slide 9

Slide 9 text

Controllable Environments

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

Uncontrollable Environments

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

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

UC Browser

Slide 20

Slide 20 text

UC Browser 400 million users 32% market-share in China

Slide 21

Slide 21 text

... to be honest ... only few of them come with their own engine

Slide 22

Slide 22 text

Under the top-most used browsers on iOS and Android

Slide 23

Slide 23 text

Fragmentation

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

No content

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

iOS screen fragmentation

Slide 29

Slide 29 text

Android screen fragmentation

Slide 30

Slide 30 text

Holy fragmentation, Batman This is friggin' scary

Slide 31

Slide 31 text

And that is just Android ...

Slide 32

Slide 32 text

Viewport is one thing... Features? Implementation quality? Memory? Resolution? Browser Speed? Connection speed?

Slide 33

Slide 33 text

What about things we trust?

Slide 34

Slide 34 text

> t r u e + t r u e 2

Slide 35

Slide 35 text

> 0 . 1 + 0 . 2 0 . 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4

Slide 36

Slide 36 text

> 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Slide 37

Slide 37 text

> [ ] = = ! [ ] t r u e

Slide 38

Slide 38 text

> t y p e o f N a N n u m b e r

Slide 39

Slide 39 text

Programming went full retard

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

-webkit-text-stroke: 4px;

Slide 42

Slide 42 text

This is madness!

Slide 43

Slide 43 text

You can't control everything

Slide 44

Slide 44 text

You can't control anything

Slide 45

Slide 45 text

Parallax Scrolling?

Slide 46

Slide 46 text

No content

Slide 47

Slide 47 text

moto.oakley.com 1. 85.4 MB page weight 2. 471 HTTP Requests 3. 2 minutes 45 seconds until loading screen replaced with content 4. 4 minutes 10 seconds to wait for onLoad event

Slide 48

Slide 48 text

There sure is a mobile version? ... oh yeah, there is...

Slide 49

Slide 49 text

85.9 MB

Slide 50

Slide 50 text

Costs Roaming in Switzerland for EU clients is 1€ per MB

Slide 51

Slide 51 text

Costs vodafone UK charges 1£ per 25 MB

Slide 52

Slide 52 text

Assumptions Features: Scrolling Implementation quality: Tried, trusted and Robust Memory: A shitload Resolution: Of course Retina! Browser Speed: iPad-near JS execution time Connection speed: Harddrive

Slide 53

Slide 53 text

Features

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

No content

Slide 56

Slide 56 text

overflow: scroll

Slide 57

Slide 57 text

-webkit-overflow-scrolling: touch

Slide 58

Slide 58 text

Feature detection Test for overflow-scrolling, otherwise use iScroll

Slide 59

Slide 59 text

var has3d = 'WebKitCSSMatrix' in window && 'm11' in new WebKitCSSMatrix()

Slide 60

Slide 60 text

The good: We did feature detects, and polyfilled in case

Slide 61

Slide 61 text

The bad: We assumed iScroll will fix all our problems iScroll assumed hardware acceleration is a good idea overall

Slide 62

Slide 62 text

The ugly: We broke IE10 on Windows Phone 8

Slide 63

Slide 63 text

No content

Slide 64

Slide 64 text

When using skrollr on mobile you don't actually scroll. When detecting a mobile browser skrollr disables native scrolling and instead listens for touch events and moves the content

Slide 65

Slide 65 text

A classic $('a').on('click', function()) { window.location.href = $(this).attr('href'); }

Slide 66

Slide 66 text

No content

Slide 67

Slide 67 text

Don't recreate browser features

Slide 68

Slide 68 text

Implementation quality

Slide 69

Slide 69 text

No content

Slide 70

Slide 70 text

-webkit-something: something

Slide 71

Slide 71 text

meta-Viewport

Slide 72

Slide 72 text

meta-Viewport

Slide 73

Slide 73 text

... not that it does anything ...

Slide 74

Slide 74 text

@media(max-width: 320px) { @ms-viewport { width: 320px } }

Slide 75

Slide 75 text

@-ms-viewport { width: device-width; }

Slide 76

Slide 76 text

Browser Speed Lightspeed

Slide 77

Slide 77 text

Truth is ... JavaScript takes long to execute

Slide 78

Slide 78 text

Pigs of Awesome - iOS

Slide 79

Slide 79 text

Pigs of Awesome - Android

Slide 80

Slide 80 text

$('.item.' + filterCriteria).each(function() { $(this).hide(); });

Slide 81

Slide 81 text

$('.filterArea').addClass('.filterCritera'); .filterCritera .hasCritera { display: none; }

Slide 82

Slide 82 text

Where is JavaScript necessary?

Slide 83

Slide 83 text

Lanyrd

Slide 84

Slide 84 text

Lanyrd User Agent Detection ... done right! Got a slow JS engine? Don't get any JS.

Slide 85

Slide 85 text

Instagram on iOS5 2/13 - 7/13

Slide 86

Slide 86 text

No content

Slide 87

Slide 87 text

No content

Slide 88

Slide 88 text

No content

Slide 89

Slide 89 text

Browsers other than Chrome don't priorize JS over IMG assets They take everything in order, to ensure nothing is missing on execution

Slide 90

Slide 90 text

Use JavaScript to load content that's only available with JavaScript

Slide 91

Slide 91 text

13s > 1.4s

Slide 92

Slide 92 text

sighjavascript.tumblr.com

Slide 93

Slide 93 text

Connection speed

Slide 94

Slide 94 text

No content

Slide 95

Slide 95 text

A though one ... but rule of thumb is to reduce requests Load content that is necessary for the first impression

Slide 96

Slide 96 text

Reduce everything!

Slide 97

Slide 97 text

What does not kill me makes me smaller

Slide 98

Slide 98 text

RESS Responsive & Server-Side

Slide 99

Slide 99 text

if ($(document).width() > 640) { $.get('path/to/html', function(data){ $('[role="complementary"]').append(data); }); }

Slide 100

Slide 100 text

Single Pager? Embed CSS and Scripts inline Use sprites and fonts Beware of base64 asset embedding

Slide 101

Slide 101 text

No content

Slide 102

Slide 102 text

Solutions Features: Use, when certain that it's there! Implementation quality: Modern features should be an add-on Browser Speed: Less JavaScript dependent content Memory: Optimize Images, reduce Image Footprint Resolution: See above, use SVG, use Responsive Images! Connection speed: Fear for worst, reduce requests!

Slide 103

Slide 103 text

Solutions Features: Progressive Enhancement Implementation quality: Progressive Enhancement Browser Speed: Progressive Enhancement Memory: Progressive Enhancement Resolution: Progressive Enhancement Connection speed: Progressive Enhancement

Slide 104

Slide 104 text

Progressive Enhancement

Slide 105

Slide 105 text

No content

Slide 106

Slide 106 text

Progressive Enhancement Provide a solid (HTML) base, something you trust and know Enhance your presentation by applying new styles Enhance further by applying behaviour with JavaScript