112
native hybrid web vs vs

Native v. Hybrid v. Web

Embed Size (px)

DESCRIPTION

My presentation for Web Directions Unplugged to talk about some of the specific costs and challenges we face when selecting a mobile development strategy.

Citation preview

Page 1: Native v. Hybrid v. Web

native hybrid web

vs vs

Page 2: Native v. Hybrid v. Web

@fling

Page 3: Native v. Hybrid v. Web

the format

Page 4: Native v. Hybrid v. Web

ask questions.get answers.

Page 5: Native v. Hybrid v. Web

my sad love story of the mobile web

Page 6: Native v. Hybrid v. Web

native hybrid web

vs vs

Page 7: Native v. Hybrid v. Web

bradfrostweb.com

Page 8: Native v. Hybrid v. Web

bradfrostweb.com

“[Brian] made me feel the same way I feel when my grandpa talks to me about surviving the Great Depression.

—Brad Frost

Page 9: Native v. Hybrid v. Web

That Guy

Page 10: Native v. Hybrid v. Web
Page 11: Native v. Hybrid v. Web
Page 12: Native v. Hybrid v. Web
Page 13: Native v. Hybrid v. Web

3:1QA : Dev

Page 14: Native v. Hybrid v. Web

For every hour spent on development, three had to

be spent in QA.

Page 15: Native v. Hybrid v. Web

mobile ux

web

Page 16: Native v. Hybrid v. Web

mobile ux

web

Page 17: Native v. Hybrid v. Web
Page 18: Native v. Hybrid v. Web

2010

Page 19: Native v. Hybrid v. Web

2010

“If the web was my religion, I feel as

though I’ve lost my faith.

Page 20: Native v. Hybrid v. Web

mobiledesign.org

Page 21: Native v. Hybrid v. Web
Page 22: Native v. Hybrid v. Web

“[Brian] states making a native application can be the best thing for a product, but confirms on the other hand that the mobile web is the only long term commercially viable content platform for mobile devices

—Thibault Imbert

Page 23: Native v. Hybrid v. Web

MADE WITH LOVE IN SEATTLE BY

Page 24: Native v. Hybrid v. Web

while my friends were rolling in cash from native apps,

Page 25: Native v. Hybrid v. Web

while my friends were rolling in cash from native apps,

I couldn’t pay my rent building web apps.

Page 26: Native v. Hybrid v. Web
Page 27: Native v. Hybrid v. Web

“I want desperately to be a web developer again, but if I have to wait until 2020 for browsers to do what Cocoa can do in 2010, I won’t wait.

—Joe Hewitt29 April 2010

Page 28: Native v. Hybrid v. Web

pinch/zoom

pinchzoom.com

Page 29: Native v. Hybrid v. Web

Price Apps!

Page 30: Native v. Hybrid v. Web

iflowreader.com

Page 31: Native v. Hybrid v. Web

iflowreader.com

“We bet everything on Apple and iOS and then Apple killed us by changing the rules in the middle of the game.

Page 32: Native v. Hybrid v. Web

suck my ass

Page 33: Native v. Hybrid v. Web

I bet everything on the web and I lost.

Page 34: Native v. Hybrid v. Web

That Guy

Page 35: Native v. Hybrid v. Web

Why?

Page 36: Native v. Hybrid v. Web
Page 37: Native v. Hybrid v. Web

MADE WITH LOVE IN SEATTLE BYMADE WITH LOVE IN SEATTLE BY

Page 38: Native v. Hybrid v. Web

computing

network

internet

devices

web

20102000199019801970 2020

mobilitypc’smainframe

MADE WITH LOVE IN SEATTLE BY

Page 39: Native v. Hybrid v. Web

computing

network

internet

devices

web

20102000199019801970 2020

ubiquitymobilitypc’smainframe

MADE WITH LOVE IN SEATTLE BY

Page 40: Native v. Hybrid v. Web

computing

network

internet

devices

web

20102000199019801970

3G

2020

2.5G2G1G

ubiquitymobilitypc’smainframe

MADE WITH LOVE IN SEATTLE BY

Page 41: Native v. Hybrid v. Web

computing

network

internet

devices

web

20102000199019801970

3G

2020

4G2.5G2G1G

ubiquitymobilitypc’smainframe

MADE WITH LOVE IN SEATTLE BY

Page 42: Native v. Hybrid v. Web

computing

network

internet

devices

web

20102000199019801970

IPv4

3G

2020

4G2.5G2G1G

ubiquitymobilitypc’smainframe

MADE WITH LOVE IN SEATTLE BY

Page 43: Native v. Hybrid v. Web

computing

network

internet

devices

web

20102000199019801970

IPv4

3G

IPv6

2020

4G2.5G2G1G

ubiquitymobilitypc’smainframe

MADE WITH LOVE IN SEATTLE BY

Page 44: Native v. Hybrid v. Web

computing

network

internet

devices

web

20102000199019801970

featurebrick

IPv4

3G

IPv6

2020

candybar

4G2.5G2G1G

ubiquitymobilitypc’smainframe

MADE WITH LOVE IN SEATTLE BY

Page 45: Native v. Hybrid v. Web

computing

network

internet

devices

web

20102000199019801970

featurebrick

IPv4

touch

3G

IPv6

2020

candybar

4G2.5G2G1G

ubiquitymobilitypc’smainframe

MADE WITH LOVE IN SEATTLE BY

Page 46: Native v. Hybrid v. Web

computing

network

internet

devices

web dot-com

20102000199019801970

web 2.0

featurebrick

IPv4

touch

3G

IPv6

2020

candybar

4G2.5G2G1G

ubiquitymobilitypc’smainframe

academia

MADE WITH LOVE IN SEATTLE BY

Page 47: Native v. Hybrid v. Web

computing

network

internet

devices

web dot-com

20102000199019801970

web 2.0

featurebrick

IPv4

touch

3G

IPv6

2020

candybar

4G2.5G2G1G

ubiquitymobilitypc’smainframe

nextacademia

MADE WITH LOVE IN SEATTLE BY

Page 48: Native v. Hybrid v. Web

computing

network

internet

devices

web dot-com

20102000199019801970

web 2.0

featurebrick

IPv4

touch

3G

IPv6

2020

candybar

4G2.5G2G1G

ubiquitymobilitypc’smainframe

nextacademia

MADE WITH LOVE IN SEATTLE BY

Page 49: Native v. Hybrid v. Web

computing

network

internet

devices

web dot-com

20102000199019801970

web 2.0

featurebrick

IPv4

touch

3G

IPv6

2020

candybar

4G2.5G2G1G

ubiquitymobilitypc’smainframe

nextacademia

MADE WITH LOVE IN SEATTLE BY

touch

IPv6

4G

ubiquity

next

Page 50: Native v. Hybrid v. Web

everything has led to this moment

Page 51: Native v. Hybrid v. Web

the future of mobile will not be the web...

Page 52: Native v. Hybrid v. Web

the future of mobile will not be the web...

...or apps

Page 53: Native v. Hybrid v. Web
Page 54: Native v. Hybrid v. Web
Page 55: Native v. Hybrid v. Web

it’s everything everywhere

Page 56: Native v. Hybrid v. Web

That Guy

Page 57: Native v. Hybrid v. Web

native hybrid web

vs vs

Page 58: Native v. Hybrid v. Web

native appAn application that is specifically written for a device platform.

Page 59: Native v. Hybrid v. Web
Page 60: Native v. Hybrid v. Web
Page 61: Native v. Hybrid v. Web
Page 62: Native v. Hybrid v. Web
Page 63: Native v. Hybrid v. Web
Page 64: Native v. Hybrid v. Web
Page 65: Native v. Hybrid v. Web
Page 66: Native v. Hybrid v. Web

“ They are expensive to create—a simple app could cost you $32,639 and take two months to create.

Page 67: Native v. Hybrid v. Web

$32,639 for a simple app2 months to create

2 weeks per feature

4 features

$8,160 per feature

Page 68: Native v. Hybrid v. Web

“A complex app could have a price tag of more than $163,200 and take six months to develop.

Page 69: Native v. Hybrid v. Web

$163,200 for a complex app6 months to create

2 weeks per feature

12 features

$13,600 per feature

Page 70: Native v. Hybrid v. Web

“ This price multiplies if you decide you want to make it available on more than one operating system.

Page 71: Native v. Hybrid v. Web

PLATFORM RESOURCES

iPhone 100%

iPad 150%

Android 175%

Honeycomb 200%

Blackberry 300%

Page 72: Native v. Hybrid v. Web

Cost of NativeSimple App Complex App

iPhone $32,639 $163,200

iPad $48,959 $244,800

Android $57,118 $285,600

Honeycomb $65,278 $326,400

Blackberry $97,917 $489,600

Total $301,911 $1,509,600

Page 73: Native v. Hybrid v. Web

hybrid appAn application using primarily web technologies inside a native container.

Page 74: Native v. Hybrid v. Web

hybrid app...to be in the App Store.

Page 75: Native v. Hybrid v. Web
Page 76: Native v. Hybrid v. Web
Page 77: Native v. Hybrid v. Web
Page 78: Native v. Hybrid v. Web
Page 79: Native v. Hybrid v. Web

Price Apps!

Page 80: Native v. Hybrid v. Web
Page 81: Native v. Hybrid v. Web

The PhoneGap Box Score

1.2 Platforms

53 ReviewsStars

Page 82: Native v. Hybrid v. Web
Page 83: Native v. Hybrid v. Web

PLATFORM RESOURCES

Hybrid iPhone 113%

Hybrid iPad 141%

Hybrid Android 225%

Hybrid Honeycomb 225%

Hybrid Blackberry 338%

Page 84: Native v. Hybrid v. Web

wtf?

Page 85: Native v. Hybrid v. Web

2.85:1QA : Dev

Page 86: Native v. Hybrid v. Web

For every hour spent on development, three has to

be spent in QA.

Page 87: Native v. Hybrid v. Web

Simple AppNative Hybrid Mobile Web

iPhone $32,639 $36,719 $24,479

iPad $48,959 $45,899 $30,599

Android $57,118 $73,438 $48,959

Honeycomb $65,278 $73,438 $48,959

Blackberry $97,917 $110,157 $73,438

Total $301,911 $339,650 $226,433

Page 88: Native v. Hybrid v. Web

Complex AppNative Hybrid Mobile Web

iPhone $163,200 $183,600 $122,400

iPad $244,800 $229,500 $153,000

Android $285,600 $367,200 $244,800

Honeycomb $326,400 $367,200 $244,800

Blackberry $489,600 $550,800 $367,200

Total $1,509,600 $1,698,300 $1,132,200

Page 89: Native v. Hybrid v. Web
Page 90: Native v. Hybrid v. Web

web appAn application that runs within a web browser.

Page 91: Native v. Hybrid v. Web

p/z universalbuild a website that provided the best possible experience to the context.

iPad

magazineiPhone

web appDesktop

website

Page 92: Native v. Hybrid v. Web
Page 93: Native v. Hybrid v. Web

Content in Context

Page 94: Native v. Hybrid v. Web
Page 95: Native v. Hybrid v. Web

MADE WITH LOVE IN SEATTLE BY

Page 96: Native v. Hybrid v. Web

1x HTML5 Markup1x Hexadecimal CSS Framework1x Typography Framework3x Javascript Frameworks12x Media-Query-based Layouts

Page 97: Native v. Hybrid v. Web

a hexadecimal what?

Page 98: Native v. Hybrid v. Web

the hex-grid

Typically when using a grid web designers are typically only using vertical units.

Page 99: Native v. Hybrid v. Web

the hex-grid

but in mobile design, we must use horizontal units as well. this means that any unit size must work vertically as well as horizontally.

Page 100: Native v. Hybrid v. Web
Page 101: Native v. Hybrid v. Web
Page 102: Native v. Hybrid v. Web

iPad

magazineiPhone

web appDesktop

website

‣ pagination was a nightmare.

‣ had to create an entirely new css framework to deal with all the screen sizes.

‣ every page had to be designed individually.

‣ content had to be type fitted, similar to print layout workflow.

‣ had to disable pinch to zoom.

‣ large image needs for iPad were brutal.

‣ had to add device detection to reduce JS page load per context.

‣ typical navigation had to be scrapped.

‣ design sacrifices had to be made to make it work.

‣ page flow was less than ideal.

Page 103: Native v. Hybrid v. Web
Page 104: Native v. Hybrid v. Web
Page 105: Native v. Hybrid v. Web

2.85:1QA : Dev

Page 106: Native v. Hybrid v. Web
Page 107: Native v. Hybrid v. Web

sni!er.pinchzoom.com

Page 108: Native v. Hybrid v. Web

Simple AppNative Hybrid Mobile Web

iPhone $32,639 $36,719 $24,479

iPad $48,959 $45,899 $30,599

Android $57,118 $73,438 $48,959

Honeycomb $65,278 $73,438 $48,959

Blackberry $97,917 $110,157 $73,438

Total $301,911 $339,650 $226,433

Page 109: Native v. Hybrid v. Web

Complex AppNative Hybrid Mobile Web

iPhone $163,200 $183,600 $122,400

iPad $244,800 $229,500 $153,000

Android $285,600 $367,200 $244,800

Honeycomb $326,400 $367,200 $244,800

Blackberry $489,600 $550,800 $367,200

Total $1,509,600 $1,698,300 $1,132,200

Page 110: Native v. Hybrid v. Web

That Guy

Page 111: Native v. Hybrid v. Web

ask questions.get answers.

Page 112: Native v. Hybrid v. Web

native? hybrid? web?

+ +