Transcript
Page 1: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Native vs

Webvs

Hybrid Mobile Development Choices

Jason Grigsby • Where 2.0 2010@grigs on Twitter • [email protected]/blog • mobileportand.com

Page 2: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices
Page 3: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices
Page 4: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Surprise Story of 2008

Flickr photo by Drift Words: http://www.flickr.com/photos/44124413076@N01/11846265/

Page 5: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Web 2.0Web-based Apps

Services & MashupsSoftware as ServiceCloud Computing

iPhone App StoreNative Apps

Few APIs between appsNo Recurring Revenue

Local Storage

Flickr photo by Civisi: http://www.flickr.com/photos/civisi/2611679744/

Page 6: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Carriers App Store

Openness

Entry Cost

Revenue Split

Restrictions

Releases

Micropayments

Closed, Seek permissionOpen to anyone

who signs agreement

Thousands of dollars $99

60/40 to 50/50 70/30

Many Few

Difficult, Timely 1 to 2 weeks

Inconsistent iTunes for every phone

What makes the App Store successful?

Page 7: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

http://blog.wired.com/gadgets/2009/02/shoot-is-iphone.html#c148364123

http://www.newsweek.com/id/174266

http://businessweek.com/@@0M43kIYQYKPISw0A/technology/content/sep2008/tc20080930_257832.htm

76 million devices

175,000 apps

3 billiondownloads

Page 8: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Gold Rush was On

Page 9: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices
Page 10: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices
Page 11: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Ringtone Apps

FYI: It shipped at $2.99. Then Justin sold his iPhone business.

http://twitter.com/justin/status/1210786170http://furbo.org/2008/12/09/ring-tone-apps/http://furbo.org/2009/02/16/raising-prices/

Page 12: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Throwaway Apps

http://www.pinchmedia.com/appstore-secrets/

Page 13: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

More Open ≠ No Gatekeeper

96%Approved

(what about that 4%?)

Page 14: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

4.6BillionMobile phone for >1/2 the planet.

Flickr photo by Pingnews: http://www.flickr.com/photos/pingnews/370061022/

Page 16: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

iPhone Only Part of World Wide Market

0

22500

45000

67500

90000

80878

34346

24889

15027

81266798

1112

Symbian RIM iPhone Windows Mobile LinuxAndroid WebOS

2009 Smartphone Sales — Thousands of Unitshttp://www.gartner.com/it/page.jsp?id=1306513

Page 17: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

iPhone Only Part of US Market — Jan 2010

http://www.comscore.com/Press_Events/Press_Releases/2010/3/comScore_Reports_January_2010_U.S._Mobile_Subscriber_Market_Share

Platform Market Share Point Change(compared to Oct 09)

RIM 43.0% 1.7

Apple 25.1% 0.3

Microsoft 15.7% -4.0

Google 7.1% 4.3

Palm 5.7% -2.1

Page 18: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Flickr photo by André-Batista: http://www.flickr.com/photo_zoom.gne?id=408700622&size=o

Objective C

Java ME

WebOS

C++

.NET Compact

BREW

Dalvik

Visual Basic

C

Symbian Windows Mobile

Palm

Page 19: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Google Mobile — App Challenges

•Pressure from CEO for rapid releases

•10+ platforms to support

•Over 100 different builds

http://www.flickr.com/photos/83731031@N00/445924458/ • http://www.flickr.com/photos/mcdave/142758127/http://www.flickr.com/photos/nataliejohnson/290541732/

Page 20: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Flickr photo by .Hessam: http://www.flickr.com/photos/essamo/1070527547/

Fragmentation:This is what the

web is supposed to solve.

Page 21: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Carriers App Store Mobile Web

Openness

Entry Cost

Revenue Split

Restrictions

Releases

Micropayments

Closed, Seek permission

Open to anyone who signs agreement

Completely Open

Thousands of dollars $99 None

60/40 to 50/50 70/30 100%

Many Few None

Difficult, Timely 1 to 2 weeks Instantaneous

Inconsistent iTunes for every phone Not yet

Mobile Web Distribution

Page 22: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Ok Hot Shot, How are You Going to Create Super Monkey Ball with HTML?

<div id=”bridge” class=”rope”>

<div id=”bubble”><span id=”monkey sprite-replace”>Monkey</span>

jquery-banana.js

Some Applications Have to Be Native

Page 23: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Five Common Reasons for Native Apps

Performance

Offline Mode

Findability

Monetization

Device Attributes

Flickr photo byboklm: http://www.flickr.com/photos/boklm/486646486/

Page 24: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Flickr: Uploaded February 11, 2007 by hawridger

1. Performance

Not for all applications

Good enough for many applications

Javascript Performance improving

Hardware Accelerated CSS

Web developers must improve

Page 25: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

We’ve Become Bandwidth Gluttons | Use YSlow

Since 2003:

• Web Page Size Tripled• # of Objects Doubled

Since 1995:

• Web Page Size: 22x• # of Objects: 21x

Source: http://www.websiteoptimization.com/speed/tweak/average-web-page/

Page 26: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

2. Offline Support

• HTML 5

• Client-side Database Storage API

• Application Cache

• Essentially SQLite in browser

• Available on iPhone since 2.0

• Google Gears, Android, Nokia soon?

Page 27: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Gmail Using HTML5

< 10 seconds on EDGE, 3 seconds on 3G

Page 28: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

http://148apps.biz

3. Findability

175,000 appsYour app will be

easy to find.

Page 29: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices
Page 30: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Flickr photo by Lyza Gardner: http://www.flickr.com/photos/lyza/49545547/

4. Monetization

Page 31: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

5. Device Attributes

Location

Camera

Address Book

Accelerometer

Compass

Page 33: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices
Page 34: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices
Page 35: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Flickr photo by Thomas Purves: http://www.flickr.com/photos/thomaspurves/744225198/

Page 36: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

http://wiki.phonegap.com/Roadmap

http://phonegap.com

Page 37: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

http://www.keypointapp.com/

What can you do with Phone Gap?

http://harmoniousapp.com/

Page 38: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Other Hybrid Approaches

• Appcelerator Titaniumhttp://www.appcelerator.com/

• QuickConnecthttp://quickconnect.pbworks.com

• Rhomobile http://rhomobile.com

• Big 5 http://big5apps.com/

Page 39: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Hybrid Apps?

Yes we can

Page 40: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

There is no right answer.

Understand your options.

Pick the best technology (or tech combo) for your needs.

Page 41: Where 2.0 — Native vs Web vs Hybrid: Mobile Development Choices

Flickr photo by Pingnews: http://www.flickr.com/photos/pingnews/370061022/

Thank You for Your Time!

@grigs on Twitter • [email protected]/blog • mobileportand.com


Top Related