NATIVE vs WRAPPED APPSWhat to build ?<br />Guilhem Ensuque<br />Twitter: @gensuque_op<br />Hashtags: #openplug, #gluecon<b...
Typical app story – episode 1<br />Boss: “I need an iPhone app !”<br />Engineer: “OK I go learn Objective-C and do it …”<b...
Boss: “Ah but… how about Android ?”<br />Engineer: “I need to learn Java !”<br />Boss: “I don’t have the money nor the tim...
LESSONS LEARNED Your mileage may vary<br />User Experience<br />Resources<br />Platforms<br />
USER EXPERIENCE<br />Tailored<br />vs<br />Generic ?<br />How does the user get my app ?<br />How much integration ?<br />
USER EXPERIENCECASE IN POINT: FACEBOOK<br />iPhone<br />app<br />iPad<br />website<br />
PLATFORMS<br />Which <br />to target<br />?<br />Tablets, TVs, cars, fridges ?<br />Smartphone vs feature phone ?<br />
PLATFORMSA BIT OF HISTORY<br />Source:<br />Asymco blog<br />
PLATFORMSWHERE IT'S GOING<br />Microsoft WM6.x/WP7<br />Nokia Symbian<br />RIM Blackberry<br />Apple iOS<br />Android<br /...
RESOURCES<br />Time <br />vs<br />Money?<br />What are my team skills ?<br />Do we have legacy code ?<br />
RESOURCESSOCRATIC APPROACH<br />“γνῶθι σεαυτόν “<br /> “Know Thyself”<br />
TECHNICAL SOLUTIONSNO SILVER BULLET<br />NATIVE <br />WEB <br />X-PLATFORM<br />WRAPPED<br />WORE<br />
WRITE ONCE RUN EVERYWHERE#FAIL<br />User Experience<br />Not Good<br />So-so<br />Resources<br />Platforms<br />Good<br />
WRAPPED WEB APPS#GOOD<br />User Experience<br />So-so<br />Resources<br />Platforms<br />Good<br />Good<br />
CROSS-PLATFORM NATIVE APPS#FTW<br />User Experience<br />Good<br />Resources<br />Platforms<br />Good<br />So-so<br />
NATIVE APPS#EXPENSIVE<br />User Experience<br />Good<br />Not Good<br />Not Good<br />Resources<br />Platforms<br />
HYBRID APPROACHANATOMY OF AN HYBRID WRAPPED/NATIVE APP<br />Native stacks & middleware<br />UI + core app logic<br />Netwo...
CONCLUSION<br />Use the right tool for the right job<br />
A bit of self-advertising<br />http://developer.openplug.com<br />
Upcoming SlideShare
Loading in …5
×

GlueCon'11 - Native vs Wrapped Mobile apps : What to Build ?

2,804 views

Published on

Presentation at GlueCon 2011 on May,25 2011.
Covering the questions developers should ask themselves before selecting from a range of technologies: native dev, cross-platform dev, wrapped web apps, write-once-run-anywhere

Published in: Technology
1 Comment
3 Likes
Statistics
Notes
No Downloads
Views
Total views
2,804
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
1
Likes
3
Embeds 0
No embeds

No notes for slide
  • Show of hands How many of you have developed a mobile app ? Who has developed for iPhone ? Who has developed for Android ? other platform ?
  • Tradeoff to be made between Resources (team available, money, time, skills, legacy code) Platforms (fragmentation, mobile vs tablet vs TV vs other, smartphonevs feature phone …) User Experience (tailored vs platform/context-specific, ease of distribution, integration with system …)
  • Good user experience drives engagement “Uncanny valley” effect : app UX has to be integrated with rest of the system, there’s no “close enough” integration, users will tell Distribution: app store vs web, issues of searchability, discoverability, monetisation
  • iPhone: native app with “close enough” to native UX, still feel disturbed as a useriPad: just a website, no app … very “uncanny”. Users expect gestures, photo gallery integration
  • Tradeoff to be made between Resources (team available, money, time, skills, legacy code) Platforms (fragmentation, mobile vs tablet vs TV vs other, smartphonevs feature phone …) User Experience (tailored vs platform/context-specific, ease of distribution, integration with system …)
  • Good resources to check:Asymco (Horace Dediu)Communities Dominate Brands (TomiAhonen)Analyst houses (Gartner, IDC, Forrester …)
  • Symbian still #1 worldwide, but major regional differences, Nokia announced its end of life after 150m units -&gt; 2012 Android explosion but fragmentation due to OEM and operator variants + non-smartphone devices: tablets, TVs, embedded systems …iOShodling steady, Apple does not care about market share but about profits (with 5% market share of all devices they make up 35% of profit) RIM declining, trying to reinvent themselves with TAT acquisition, QNX, Playbook, HTML5, Android apps on BB -&gt; looks like Nokia 3 years ago WP7: nice and cool, but low penetration, will Nokia help ?
  • Tradeoff to be made between Resources (team available, money, time, skills, legacy code) Platforms (fragmentation, mobile vs tablet vs TV vs other, smartphonevs feature phone …) User Experience (tailored vs platform/context-specific, ease of distribution, integration with system …)
  • Skills: C/C++/Obj-C, OpenGL, Java, J2ME, Android Java, Blackberry Java, Flash Lite, Flash, AIR, Silverlight/.NET/C#, Lua, Ruby, Javascript, HTML5/CSS3 Code reuse Tradeoff between time and money “GnotiSeoton” : Know Yourself – ask yourself the right questions, no single right or wrong answers
  • Wide spectrum of options Web site- “Write-once-run-everywhere” app: web app, Flash/AIR, Java/J2ME, Silverlight Wrapped web app: HTML5 + Sencha/jQueryMobile + PhoneGap/Apparat.io; BrightcoveAppCloud ?, RIM WebWorks, Nokia WRT, WAC Cross-platform native app: OpenPlug, Appcelerator, MonoTouch Native app: iOS SDK/xCode, Android SDK, BB SDK, Nokia S60 Carbide SDK
  • Technologies: Java, Flash/AIR, SilverlightAdvantages:Single devSame user experience on all devicesDrawbacks:Poor performanceUI not consistent with rest of platform“Uncanny Valley” effectCannot be distributed on all platforms/app stores (notably Apple)
  • Technologies: HTML5/CSS3, Frameworks:Sencha/jQuery Mobile, native extensions: PhoneGap, packaging: PhoneGap, Apparat.ioAdvantages:Single code baseUser experience tailoredCan be distributed on all platforms/app stores (notably Apple)Drawbacks:Performance so-so, getting better with faster JS enginesUI closeness dependent on selected framework, not quite there ?
  • Technologies: Alcatel-Lucent OpenPlug, Appcelerator Titanium , Novell MonoTouchAdvantages:Single code base / dev skill setUser experience adapted to platformVery good performanceDistribution through app storesDrawbacks:None ?Depends on your socratic answers
  • Technologies: Alcatel-Lucent OpenPlug, Appcelerator Titanium , Novell MonoTouchAdvantages:Single code base / dev skill setUser experience adapted to platformVery good performanceDistribution through app storesDrawbacks:None ?Depends on your socratic answers
  • GlueCon'11 - Native vs Wrapped Mobile apps : What to Build ?

    1. 1. NATIVE vs WRAPPED APPSWhat to build ?<br />Guilhem Ensuque<br />Twitter: @gensuque_op<br />Hashtags: #openplug, #gluecon<br />Slides: http://slideshare.net/gensuque<br />
    2. 2. Typical app story – episode 1<br />Boss: “I need an iPhone app !”<br />Engineer: “OK I go learn Objective-C and do it …”<br />Engineer (3 months later) : “Done !”<br />
    3. 3. Boss: “Ah but… how about Android ?”<br />Engineer: “I need to learn Java !”<br />Boss: “I don’t have the money nor the time for that!”<br />Typical app story – episode 2<br />
    4. 4. LESSONS LEARNED Your mileage may vary<br />User Experience<br />Resources<br />Platforms<br />
    5. 5. USER EXPERIENCE<br />Tailored<br />vs<br />Generic ?<br />How does the user get my app ?<br />How much integration ?<br />
    6. 6. USER EXPERIENCECASE IN POINT: FACEBOOK<br />iPhone<br />app<br />iPad<br />website<br />
    7. 7. PLATFORMS<br />Which <br />to target<br />?<br />Tablets, TVs, cars, fridges ?<br />Smartphone vs feature phone ?<br />
    8. 8. PLATFORMSA BIT OF HISTORY<br />Source:<br />Asymco blog<br />
    9. 9. PLATFORMSWHERE IT'S GOING<br />Microsoft WM6.x/WP7<br />Nokia Symbian<br />RIM Blackberry<br />Apple iOS<br />Android<br />Worldwide Mobile OS Marketshare 2011 <br />(source: Gartner)<br />
    10. 10. RESOURCES<br />Time <br />vs<br />Money?<br />What are my team skills ?<br />Do we have legacy code ?<br />
    11. 11. RESOURCESSOCRATIC APPROACH<br />“γνῶθι σεαυτόν “<br /> “Know Thyself”<br />
    12. 12. TECHNICAL SOLUTIONSNO SILVER BULLET<br />NATIVE <br />WEB <br />X-PLATFORM<br />WRAPPED<br />WORE<br />
    13. 13. WRITE ONCE RUN EVERYWHERE#FAIL<br />User Experience<br />Not Good<br />So-so<br />Resources<br />Platforms<br />Good<br />
    14. 14. WRAPPED WEB APPS#GOOD<br />User Experience<br />So-so<br />Resources<br />Platforms<br />Good<br />Good<br />
    15. 15. CROSS-PLATFORM NATIVE APPS#FTW<br />User Experience<br />Good<br />Resources<br />Platforms<br />Good<br />So-so<br />
    16. 16. NATIVE APPS#EXPENSIVE<br />User Experience<br />Good<br />Not Good<br />Not Good<br />Resources<br />Platforms<br />
    17. 17. HYBRID APPROACHANATOMY OF AN HYBRID WRAPPED/NATIVE APP<br />Native stacks & middleware<br />UI + core app logic<br />Network APIs <br />and generic libs<br />
    18. 18. CONCLUSION<br />Use the right tool for the right job<br />
    19. 19. A bit of self-advertising<br />http://developer.openplug.com<br />

    ×