mobile stategy
DESCRIPTION
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.TRANSCRIPT
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:
Businesses can no longer afford
to ignore it
1. Mobile (Native) Apps – Develop for multiple platform
2. Mobile web apps (Responsive Web Design) –Should work on most of the device
3. Hybrid apps – best of both world ( 1 & 2)4. Content Transformation – Not always best
experience 5. Do nothing –
Native AppsWeb Apps
Native Apps
Hybrid Apps
What are these options ??
Native Application
Language Objective-C,C,C++
Java(Some C, C++) Java C#, VB.NET
Tools Xcode Android SDK BB Java Eclipse Plug-In
Visual-Studio,Windows Phone
Dev Tool
Packing Format .app .apk .cod .xap
Application Stores
Source Code for Apple iOSObjective-C,
C, C++Resources
(images etc)
Xcode IDEComplier,
LinkerPackage
Executable (Binary)
*.app Package
Source Code for AndroidJava (some
C, C++)Resources
(images etc)
Android SDKComplier,
LinkerPackage
Executable (Binary)
*.apk Package
Source Code for Blackberry OS
JavaResources
(images etc)
BB Java Eclipse Plug-inComplier,
LinkerPackage
Executable (Binary)
*.cod Package
Source Code for WindowsC#, VB.NET and more
Resources (images etc)
Visual Studio, Win Phone Dev ToolsComplier,
LinkerPackage
Executable (Binary)
*.xap Package
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
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
Mobile Web Application
Responsive Web Design
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
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
Hybrid Application
Image Source: PhoneGap
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
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
Need skill set for mobile framework (PhoneGap, Titanium..)
Performance depends on device’s browser capabilities
Can’t handle heavy graphics
Comparison / Summary
Native Web App HybridSkills/tools needed for cross-platform apps
• Objective-C• Java • C, C++, C#• VB.net
• HTML • CSS • JavaScript
• HTML • CSS • JavaScript• Mobile framework
Time to market Slow Fast Moderate
Device access
Full access:(Camera, microphone, GPS, Calender, Contacts, Notification, gyroscope, accelerometer, file upload, etc…)
Limited (GPS, gyroscope, file upload)
Full access:(Camera, microphone, GPS, Calender, Contacts, Notification, gyroscope, accelerometer, file upload, etc…)
Graphics Native APIs HTML, Canvas, SVG HTML, Canvas, SVG
Native look & feel Native Emulated Emulated
Distribution Appstore Internet/Web Appstore
Pinch, spread Yes No Yes
Connectivity Online and offline Mostly online Online and offline
Which way to go?
Sector Requirement Possible Option
GamesQuick response, Local run time environment, Access to device components Native Apps
Retail
Ongoing updates, Rich graphics, Product scanning, payment integration, local storage Hybrid Apps
Social Networking
Access to push notification, ability to run in background, integration to camera, LBS, discovery Hybrid Apps
Banking & Finance
Multiple security layers, ability to run offline, offline storage, access to NFC, push notification, simple and easy interface Native Apps
NewsEasy access, multimedia, ongoing updating Web Apps
Loyalty Syncing of customer data, push notification, immediate access, high analytics, Web Apps
Image Source: Developerforce