http://hu.tt

WebPlatform

First a flashback

The stack

Server-sided architecture

Browser = Document reader

Description
W3C

Shift in standard bodies

Description Description
W3C & WHATWG

Story: How did we get the HTML5 logo?

January 18, 2011

CNET: "W3C's new logo promotes HTML5--and more"

"The logo is a general-purpose visual identity for a broad set of open Web technologies, including HTML5, CSS, SVG, WOFF, and others,"

January 19, 2011

WHATWG: "HTML is the new HTML5"

"... we moved to a new development model, where the technology is not versioned and instead we just have a living document that defines the technology as it evolves."

January 19, 2011

January 22, 2011

New development model.

WHATWG HTML Spec.

Description
W3C

Web applications

Browser = application runtime

What has happend to the platform?

Description

No more plugins

Description

Responsive web

Description

JavaScript performance. Solved.

Description
ejohn.org/blog/javascript-performance-rundown/

JavaScript performance. Solved.

Description
hacks.mozilla.org/2013/12/gap-between-asm-js-and-native-performance-gets-even-narrower-with-float32-optimizations/

Browser usage has shifted.

Description

More consistent rendering.

Continuous deployment.

What about the way we build apps?

From server-sided architecture

Description
LinkedIn

From server-sided frameworks

Description Description

Towards client-sided architecture

Description
LinkedIn

Towards client-sided frameworks

Description Description

Description

JavaScript is everywhere

Description

Unified code-bases.

Description

What about mobile?

Opera Mini

Description

Safari 7

Description

Facebook and HTML5

Description

And it's problems...

Description

Said about HTML5

... When I'm introspective about the last few years I think the biggest mistake that we made, as a company, is betting too much on HTML5 as opposed to native... because it just wasn't there....
Mark Zuckerberg
Facebook

W3C Core Mobile Web Platform Group

Identified problems

  • Rendering
    • FPS / GPU
  • Assets
    • Delivery
    • Unloading images
  • Network/Caching/Storage
    • AppCache is unusable.
    • Reliable way to detect network.
  • Tooling
    • Debugging / Blackboxes

Said about HTML5...continued

... I'm actually, on long-term, really excited about it. One of the things that's interesting is we actually have more people on a daily basis using mobile Web Facebook than we have using our iOS or Android apps combined. So mobile Web is a big thing for us.
Mark Zuckerberg
Facebook

Mobile is damn important.

Mobile usage

What is mobile web?

We shouldn’t think of “the web” as only what renders in web browsers. We should think of the web as anything transmitted using HTTP and HTTPS. Apps and websites are peers, not competitors. They’re all just clients to the same services.
John Gruber
http://daringfireball.net/2014/04/rethinking_what_we_mean_by_mobile_web

We are in a transition phase.

Mobile market shares

http://www.comscoredatamine.com/2014/04/smartphone-market-led-by-android-in-software-iphone-in-hardware/

My homescreen

Rendering and packaging.

So, what's happening?

WebGL is changing rendering.

ASM.js is making games possible

WebRTC is changing realtime.

ServiceWorkers are changing offline.

WebComponents are solving modularity.

FirefoxOS & ChromeOS are solving packaging.

HTTP 2.0/SPDY is solving distribution.

http://chimera.labs.oreilly.com/books/1230000000545/ch12.html#REQUEST_RESPONSE_MULTIPLEXING

The web is updating every 6th week

It's here to stay.

Thanks.