Robert O’Callahan - The Open Web Platform in the mobile era

Slide 1

Slide 1 text

Robert O'Callahan Mozilla Corporation The Open Web Platform In The Mobile Era

Slide 2

Slide 2 text

Let's make this interactive.

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

The “open Web platform”: true multi-vendor standards.

Slide 7

Slide 7 text

But vendors want to own the platform.

Slide 8

Slide 8 text

No content

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

No content

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

Does the Web really compete with native platforms? Yes.

Slide 15

Slide 15 text

Single-vendor platforms address real needs. For example: slick UI, sensors, offline usage, app discovery and monetization, tooling.

Slide 16

Slide 16 text

Good news: Web standards are moving faster than ever.

Slide 17

Slide 17 text

Soon latest versions of all major browsers will support ● HTML5 Forms, Drag&Drop, parsing, , History, AppCache ● DOM touch events, orientation events, geolocation, File API, Workers ● WebSockets, EventSource ● CSS hyphenation, columns, 2D and 3D transforms, gradients, transitions and animations, flexbox layout, fonts (WOFF) ● Accelerated 2D canvas ● WebGL (Not Microsoft, but they'll crack) ● JS Typed Arrays

Slide 18

Slide 18 text

Behold demos.

Slide 19

Slide 19 text

A lot more is coming. ● JS language improvements (WeakMap, modules) ● Ongoing JS performance improvements ● IndexedDB ● CSS regions, grids, exclusions, Opentype control, element() images ● Custom CSS/SVG filters ● Fullscreen, MouseLock ● SPDY, CSP ● MediaStream, WebRTC, PeerConnection ● Some kind of audio processing

Slide 20

Slide 20 text

The Web standards platform is not stagnating. We have other problems.

Slide 21

Slide 21 text

“Browser X implements Y, browser Z doesn't” is easy to market. Especially if you produce apps that use Y. This creates bad incentives.

Slide 22

Slide 22 text

Maybe the feature isn't a true multi-vendor standard. Please beware of “open- washing”.

Slide 23

Slide 23 text

Maybe the feature is poorly implemented.

Slide 24

Slide 24 text

Maybe the feature is just bad for the Web.

Slide 25

Slide 25 text

Please be discerning about new features.

Slide 26

Slide 26 text

Less marketable activities are as important as adding new features, e.g. improving specs and fixing bugs to improve interop.

Slide 27

Slide 27 text

Please give us the right incentives by focusing on implementation and spec quality.

Slide 28

Slide 28 text

Not Webkit.

Slide 29

Slide 29 text

Apps that target a particular browser engine are antithetical to the open Web. Please don't do that.

Slide 30

Slide 30 text

if (window.has3d) { elem.setAttribute('style', '-webkit-transform:translate3d(' +x+'px,'+y+'px,'+z+'px);'); }

Slide 31

Slide 31 text

Vendor prefixing has served us well but it can hurt. We need to unprefix features quicker. Please treat prefixed features as experimental.

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

Apps locked into single-vendor distribution channels undermine the open Web. Please don't do that.

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

No content

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

Facebook should not have a monopoly on Web identity. Mozilla is creating BrowserID. Please use it.

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

A drive for open Web standards is more needed than ever. Even if HTML wins, the open Web could lose. Please be responsible.