What Lies Ahead for HTML5

98
What Lies Ahead for HTML5? Krzysztof Szafranek Wooga GmbH @szafranek
  • date post

    20-Oct-2014
  • Category

    Technology

  • view

    728
  • download

    1

description

Presentation about web and native applications with the focus on mobile from the OOP 2013 conference in Munich.

Transcript of What Lies Ahead for HTML5

Page 1: What Lies Ahead for HTML5

What Lies Ahead for HTML5?

Krzysztof SzafranekWooga GmbH

@szafranek

Page 2: What Lies Ahead for HTML5

[ˈkʂɨʂtɔf ʂafranˈɛk]Web application

&game developer

Wooga(Roche, Nokia)

Let me start with the most technically difficult part of the presentation.

Page 3: What Lies Ahead for HTML5

How many of you would consider yourself developers?How many of you have used HTML5?

Page 4: What Lies Ahead for HTML5

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.

Last year’s quote that caused a lot of confusion

Page 5: What Lies Ahead for HTML5

The language

< >

Page 6: What Lies Ahead for HTML5

Next iteration of the HTML language

Markup language for structuring and presenting content for the World Wide Web.

Page 7: What Lies Ahead for HTML5

<video>

<audio>

Page 8: What Lies Ahead for HTML5

<canvas>

Page 9: What Lies Ahead for HTML5

New form elements

<input type=color>

<input type=date>

How many of you have implemented a date picker?

Less code to improve site’s usabilityFaster site

Page 10: What Lies Ahead for HTML5

The buzzword

[5]

Page 11: What Lies Ahead for HTML5

3D

WebGLDemo: 3D race car

Page 12: What Lies Ahead for HTML5

Media

video, audioScreenshot: mobile YouTube

Page 13: What Lies Ahead for HTML5

Offline

Screenshot: Twitter mobile

Page 14: What Lies Ahead for HTML5

CSS3

Page 15: What Lies Ahead for HTML5

Network

WebSockets, server-sent events, XHR2Screenshot: Facebook chat

Page 16: What Lies Ahead for HTML5

Devices

Microphone, cameraDemo: speech recognition

Page 17: What Lies Ahead for HTML5

HTML5has already

won

If you have a website built in the last 3 years, most likely you’ve been using HTML5 already.

Page 18: What Lies Ahead for HTML5

http://html5awesome.com/

Page 19: What Lies Ahead for HTML5

mobile

[15]Mobile doesn’t necessarily mean phone!

Page 20: What Lies Ahead for HTML5

0

7.5

15

22.5

30

% of sales done through mobile

16.269.84 2011

2012

Black Friday 2012

Source: http://www-01.ibm.com/software/marketing-solutions/benchmark-reports/benchmark-2012-black-friday.pdf

Page 21: What Lies Ahead for HTML5

0

7.5

15

22.5

30

% of traffic coming from mobile

24.04

14.3320112012

Black Friday 2012

Page 22: What Lies Ahead for HTML5

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.

Page 23: What Lies Ahead for HTML5

... 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.

Page 24: What Lies Ahead for HTML5

Web or native?

Page 25: What Lies Ahead for HTML5

Native

Page 26: What Lies Ahead for HTML5

Native

Page 27: What Lies Ahead for HTML5

Native

Performance

Page 28: What Lies Ahead for HTML5

Native

Page 29: What Lies Ahead for HTML5

Native

Page 30: What Lies Ahead for HTML5

Access to device features

Native

Page 31: What Lies Ahead for HTML5

Native

Page 32: What Lies Ahead for HTML5

Native

Page 33: What Lies Ahead for HTML5

Distribution throughan app store

Native

Page 34: What Lies Ahead for HTML5

Native

Page 35: What Lies Ahead for HTML5

Native

Page 36: What Lies Ahead for HTML5

Payments

Native

Page 37: What Lies Ahead for HTML5

Native

Page 38: What Lies Ahead for HTML5

Opportunity cost

Page 39: What Lies Ahead for HTML5

Apple

Samsung

HTC

Nokia

RIM Sony

LGAmazon

m.guardian.co.uk

3.3m daily page viewsApple 80%Samsung 8%RIM 6%HTC 5%Nokia 1%

http://www.guardian.co.uk/info/developer-blog/2012/dec/11/fragmented-world-mobile-traffic-data

Page 40: What Lies Ahead for HTML5

Discoverability

Discoverability in the AppStore,over 700 000 apps.

Page 41: What Lies Ahead for HTML5

Development cost

1.3 million Android devices is being activated every single day.Source: http://techcrunch.com/2012/09/05/eric-schmidt-there-are-now-1-3-million-android-device-activations-per-day/

Page 42: What Lies Ahead for HTML5

Web

Page 43: What Lies Ahead for HTML5

Web

Page 44: What Lies Ahead for HTML5

Web

You already have it

Page 45: What Lies Ahead for HTML5

Web

Page 46: What Lies Ahead for HTML5

Web

Page 47: What Lies Ahead for HTML5

Web

Cheaper to build

Page 48: What Lies Ahead for HTML5

Web

Page 49: What Lies Ahead for HTML5

Web

Open standards not controlled by one company

Page 50: What Lies Ahead for HTML5

Web

Vendor independence

Open standards not controlled by one company

Page 51: What Lies Ahead for HTML5

Web

Open standards not controlled by one company

Page 52: What Lies Ahead for HTML5

Web

Page 53: What Lies Ahead for HTML5

Web

Easy updates

Page 54: What Lies Ahead for HTML5

Web

Page 55: What Lies Ahead for HTML5

Web

Page 56: What Lies Ahead for HTML5

Web

Future proof

Page 57: What Lies Ahead for HTML5

Web

Page 58: What Lies Ahead for HTML5

Discoverability

Page 59: What Lies Ahead for HTML5

Payments

Page 60: What Lies Ahead for HTML5

“Standards”

Page 61: What Lies Ahead for HTML5

Hybrid

Page 62: What Lies Ahead for HTML5

Hybrid

HTML5 inside

Native wrapper

Page 63: What Lies Ahead for HTML5

Hybrid

Page 64: What Lies Ahead for HTML5

Hybrid

Page 65: What Lies Ahead for HTML5

Hybrid

App store distribution

Access to device

features

Page 66: What Lies Ahead for HTML5

Hybrid

Page 67: What Lies Ahead for HTML5

Hybrid

Page 68: What Lies Ahead for HTML5

Hybrid

Cross platform

Notnative!

Page 69: What Lies Ahead for HTML5

Hybrid

Page 70: What Lies Ahead for HTML5

The story of

[30]

Page 71: What Lies Ahead for HTML5
Page 72: What Lies Ahead for HTML5

Hybrid: HTML5+PhoneGap

Over 20x less than my current game in Objective C

Page 73: What Lies Ahead for HTML5

Hybrid: HTML5+PhoneGap

22k lines of JS

Over 20x less than my current game in Objective C

Page 74: What Lies Ahead for HTML5

AppStore, worldwide

Released as open source

Page 75: What Lies Ahead for HTML5

github.com/wooga/Pocket-Island

Page 76: What Lies Ahead for HTML5

JavaScript!

Page 77: What Lies Ahead for HTML5

JavaScript!

•Development speed

Page 78: What Lies Ahead for HTML5

JavaScript!

•Developer talent

•Development speed

Page 79: What Lies Ahead for HTML5

JavaScript!

•Community

•Developer talent

•Development speed

Page 80: What Lies Ahead for HTML5

“Write once, run everywhere”

Page 81: What Lies Ahead for HTML5

“Run everywhere” – either a lie or programs that worked equally badly everywhere

Page 82: What Lies Ahead for HTML5

Sound, multitouch...

Sounds has been fixed in Safari 6, multitouch is being standardized right now.

Page 83: What Lies Ahead for HTML5

Performance

12 FPS instead of 60

Page 84: What Lies Ahead for HTML5

Conclusions

The web wasn’t the best platform for making mobile games in 2012.

[40]

Page 85: What Lies Ahead for HTML5

“Every new generation brings radical new features, and the Web will always be behind on those. So the cutting edge is native.”

Ian Hickson,editorof the HTML spec

Do you really need the cutting edge?Are you willing to pay for it?

Page 86: What Lies Ahead for HTML5

Games

Page 87: What Lies Ahead for HTML5

Games

Page 88: What Lies Ahead for HTML5

Games

Page 89: What Lies Ahead for HTML5

Games

Page 90: What Lies Ahead for HTML5

Games

Page 91: What Lies Ahead for HTML5

Operating system!

Page 92: What Lies Ahead for HTML5

WebAPIWebSMSWebTelephonyPower ManagementDevice StorageWebPaymentCameraCalendarWebBluetoothVibration API...

https://wiki.mozilla.org/WebAPI