Mobile stategy


Published on

It’s accepted that one can’t ignore mobile as channel for online presence. Major approaches are Web, Native & Hybrid. Lots of views on each approach. What are these approaches? Which one to pick & why? Should I choose one among these because it has better adaptability? Would that be right fit? Would it meet current & future roadmap?
This presentation is an attempt to answer these questions.
Comments & reviews are highly appreciated.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Mobile stategy

  1. 1. The best option for business? Burhan Surti
  2. 2.  Mobile Showrooming grow 134% during 2012 Holiday Season 2012 holiday season, there will be 48 million shoppers—about 20% of the U.S. adult population will use their smartphones to compare prices and research products while shopping in stores, a practice known as“Showrooming,” - Internet Retailer:
  3. 3. Businesses canno longer afford to ignore it
  4. 4. 1. Mobile (Native) Apps – Develop for multiple platform2. Mobile web apps (Responsive Web Design) – Should work on most of the device3. Hybrid apps – best of both world ( 1 & 2)4. Content Transformation – Not always best experience5. Do nothing –
  5. 5. Native Apps WebNative Apps Apps Hybrid Apps
  6. 6. What are these options ??
  7. 7. Native Application
  8. 8. Objective- JavaLanguage Java C#, VB.NET C,C,C++ (Some C, C++) Visual-Studio, BB Java EclipseTools Xcode Android SDK Windows Phone Plug-In Dev ToolPacking .app .apk .cod .xapFormatApplicationStores
  9. 9. Source Code for Apple iOS Source Code for Android Objective-C, Resources Java (some Resources C, C++ (images etc) C, C++) (images etc) Xcode IDE Android SDKComplier, Executable Complier, Executable Package Package Linker (Binary) Linker (Binary) *.app Package *.apk Package Source Code for Windows Source Code for Blackberry OS C#, VB.NET Resources Resources and more (images etc) Java (images etc) Visual Studio, Win Phone Dev Tools BB Java Eclipse Plug-in Complier, Executable Package Complier, Executable Linker (Binary) Package Linker (Binary) *.xap Package *.cod Package
  10. 10.  Covers all platform hence potential larger customer base Better performance Customized and smoother interface user experience Store more data offline Access to the device’s hardware and OS features – (Camera, Notifications, Contacts, calendar, Offline storage, Geo-location) Available offline
  11. 11.  Expensive/time consuming as need to develop for each platform Multiple code base to develop/maintain Requires different skill set Available via app store only – Approval Not visible to search engines
  12. 12. Mobile Web Application
  13. 13. Responsive Web Design
  14. 14.  Accessed by browser of the device hence works on any platform Quick time to market Single codebase – less effort to develop & maintain No app store distribution – No approval Search engine discoverable
  15. 15.  No access to device hardware or OS features Lower performance Limited/No local storage No platform specific look N feel No offline availability Need to support multiple browser per device
  16. 16. Hybrid Application
  17. 17. Image Source: PhoneGap
  18. 18.  Like native apps, run on the device Written with web technologies (HTML5, CSS and JavaScript). Hybrid apps run inside a native container, leverage the device’s browser engine (but not the browser) to render the HTML and process the JavaScript locally. A web-to-native abstraction layer enables access to device capabilities
  19. 19.  Experience like Native apps Combination of Native + Mobile web app Lower development cost & time Access to the device’s hardware and OS features – (Camera, Notifications, Contacts, calendar, Offline storage, Geo-location) Local storage Moderate performance
  20. 20.  Need skill set for mobile framework (PhoneGap, Titanium..) Performance depends on device’s browser capabilities Can’t handle heavy graphics
  21. 21. Comparison / Summary
  22. 22. Native Web App Hybrid • Objective-C • HTMLSkills/tools needed • Java • HTML • CSSfor cross-platform • C, C++, C# • CSS • JavaScriptapps • • JavaScript • Mobile frameworkTime to market Slow Fast Moderate Full access: Full access: (Camera, microphone, (Camera, microphone, GPS, Calender, Contacts, GPS, Calender, Contacts, Notification, gyroscope, Notification, gyroscope, accelerometer, file Limited (GPS, accelerometer, fileDevice access upload, etc…) gyroscope, file upload) upload, etc…)Graphics Native APIs HTML, Canvas, SVG HTML, Canvas, SVGNative look & feel Native Emulated EmulatedDistribution Appstore Internet/Web AppstorePinch, spread Yes No YesConnectivity Online and offline Mostly online Online and offline
  23. 23. Which way to go?
  24. 24. Sector Requirement Possible Option Quick response,Games Local run time environment, Access to device components Native Apps Ongoing updates, Rich graphics,Retail Product scanning, payment integration, local storage Hybrid Apps Access to push notification,Social ability to run in background,Networking integration to camera, LBS, discovery Hybrid Apps Multiple security layers, ability to run offline,Banking & offline storage,Finance access to NFC, push notification, simple and easy interface Native Apps Easy access,News multimedia, ongoing updating Web AppsLoyalty Syncing of customer data, push notification, immediate access, high analytics, Web Apps
  25. 25. Image Source: Developerforce
  26. 26. Questions? Pls. send