Successfully reported this slideshow.

E boerger web-hybrid_mobile_10-31-2012_slideshare

573 views

Published on

With the mobile market and app adoption skyrocketing, all companies are under pressure to enter the mobile marketplace. With the vast array of end-user devices, operating systems and user expectations, choosing the right development platform can be daunting.

In this 20-minute webinar, we will discuss the 3 main methodologies used in enterprise mobile web development – HTML5, Native or a Hybrid application development approach and the challenges and considerations for each. Join industry pioneer Eileen Boerger, President of CorSource Technology Group as she discusses:

- Key features, use-cases, and security considerations for mobile development
- How your platform choice is driven by timing, the market, and the purpose of your app
- The Pros and Cons of web, native or hybrid development

  • Be the first to comment

  • Be the first to like this

E boerger web-hybrid_mobile_10-31-2012_slideshare

  1. 1. YOUR PATH TO MOBILEEileen Boerger DEVELOPMENT DILEMMA : PresidentOctober 31, 2012 WEB, NATIVE, OR HYBRID?
  2. 2. WHY MOBILE? There are 5.9 billion mobile subscribers - 87% of the world population (ITU) 600 million new smartphones will be shipped in 2012 (Morgan Stanley) Over 1 billion feature (non-smart) phones will be shipped in 2012 (IDC) In 2012, mobile device usage eclipsed desktop usage 5
  3. 3. MOBILE USAGE IS MORE THAN JUST PHONE CALLS 94 % Accessing websites Using mobile apps Interface to enterprise applications Playing Games Watching Videos Reading the news & other media content 6
  4. 4. DEFINITIONS
  5. 5. WEB, NATIVE, OR HYBRID MOBILE APP?
  6. 6. KEY PLANNING CONSIDERATIONS Planning Area Key ConsiderationsPurpose of mobile app o Standalone, interface to enterprise app? o Target market? o Time to market?Mobile user and o Who are the targeted users?functional o What functionality do you want to provide?requirements o Need for device-specific features (camera, GPS,…)? o Online, offline access?Data access o What are the data requirements of the mobile app? o Data on mobile device, in cloud, hybrid …?Mobile platforms to o Smartphones, Tablets, …?support o iOS, Android, Windows Mobile, …?Security o How will authentication and authorization work? o Single-user devices or multi-user devices?Distribution and o App store, internet, …?Monetization o Free, one-time fee, transaction-based fee, …?
  7. 7. KEY DESIGN CONSIDERATIONS Design Area Key ConsiderationsDevice types o Screen size and resolution (DPI) o CPU performance, memory and storage space o Development tools o Special needs (GPS or camera, for example)Network constraints o Occasional connections and/or low bandwidth o Choose protocols based on speed and power consumptionUI design o Delightful user experience o Different screen sizes of devices o Security - access, authenticationArchitecture o Web app or native app or hybrid o Multi-layered architectureDevice constraints o Battery life, memory size, processor speed
  8. 8. WEB APP VS. NATIVE APP VS. HYBRID Web App Hybrid App Native App Manageable Server and Rich UX Unique Processing Distribution Easy Geo-location No Video Distribution Limited Reach OS Little OS Extensive Browser-Free IntegrationIntegration Reach Zero Camera High Portability No Camera Portability Video Online Mode Offline Mode Online and Offline
  9. 9. WEB APP - PROS AND CONS
  10. 10. NATIVE APP – PROS AND CONS
  11. 11. HYBRID APP – PROS AND CONS
  12. 12. Architectural Choices TIME TO CROSS ALL PLATFORMS Gartner, 201215 “Beyond the Wireless Tether” - Gartner Catalyst 2012
  13. 13. HTML5 FEATURESHTML5 Feature iOS Android Chrome Blackberry Windows Safari Browser Browser Phone IEGeo-locationCanvasAudioVideoTouch EventsCacheWeb StorageWeb SocketsServer-SentCSS TransitionWeb Notifications
  14. 14. BEST USES FOR EACH MOBILE APP TYPE Mobile App Type Recommended Best Uses Web App o Business-focused apps that do not need to access mobile device features, e.g., camera o General non-game apps (consumer) o Initial mobile offering Native App o Apps that require a highly-graphic interface or rich user experience o Apps that require use of mobile device features, e.g., camera o Games Hybrid App o Apps that require a moderate graphic interface o Apps that require use of mobile device features, e.g., camera
  15. 15. CASE STUDY
  16. 16. CASE STUDY – RETAIL NATIVE APP
  17. 17. CASE STUDY - DEVELOPMENT CHALLENGES Challenge Key ConsiderationsDevelopment technology o Chose to work with SDKs of native OS platformschoice o Multi-threading not available at the time on framework client wantedo Framework vs Native OS to useDevice memory constraints o Chose to work with SDKs of native OS platforms o Multi-threading not available at the time on framework client wanted to useMultiple platform development o Chose to work with SDKs of native OS platformso iOS Android o Multi-threading not available at the time on framework client wantedo SmartPhones, Tablets to useSmartPhone vs Tablet form o Look and feel tailored to each form factor (what works on Tabletfactor may not be suitable for SmartPhone)Internationalization/ o Look and feel, language support, forms of addresses, …LocalizationOn-going support of mobile o Keeping up with updates to OS versionsapps o Compatibility testing
  18. 18. CASE STUDY – MOBILE CLIENT Select Edit images Images Shopping Cart Flow
  19. 19. SUMMARY: WEB, NATIVE, OR HYBRID
  20. 20. Presented by: THANK YOU Eileen Boerger eboerger@corsource.com CorSource Technology provides consulting, software www.CorSource.com development services and technical staffing that businessesneed to succeed in the fast-moving, highly competitive worldof software development and IT. CorSource provides services to SMBs and ISVs nationwide. Learn more at www.corsource.com, and follow us on Twitter: @corsource.

×