YOUR PATH TO MOBILEDEVELOPMENT DILEMMA :WEB, NATIVE, OR HYBRID?

Eileen BoergerPresident

October 31, 2012

The Opportunity CostsThere 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

WHY MOBILE?

5

How are people using mobile?

Accessing websites

Using mobile apps

Interface to enterprise applications

Playing Games

Watching Videos

Reading the news & other media content

MOBILE USAGE IS MORE THAN JUST PHONE CALLS

94%

6

4

Web appBrowser-based app written for mobile device (separate app for mobile or responsive web app for mobile and PC)

Developed with web technologies (HTML5, Javascript, …)

Native appRuns on “native” OS, e.g., iOS, Android, Windows Mobile

Separate version of app for each OS

Developed with platform SDKs

Distributed through app store

Hybrid appRuns on “native” OS using browser engine

Developed with web technologies (HTML5, Javascript, …) and a mobile development framework (such as PhoneGap)

Distribution through app store

DEFINITIONS

5

Questions to considerPurpose of mobile app

Features of mobile app

Distribution and monetization of mobile app

Time to market

Development cost

Development technologies vs development skills

WEB, NATIVE, OR HYBRID MOBILE APP?

This is not just a technical question.

6KEY 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 functional requirements

o Who are the targeted users?o What functionality do you want to provide?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 support

o Smartphones, Tablets, …?o iOS, Android, Windows Mobile, …?

Security o How will authentication and authorization work?o Single-user devices or multi-user devices?

Distribution and Monetization

o App store, internet, …?o Free, one-time fee, transaction-based fee, …?

7KEY DESIGN CONSIDERATIONS

Design Area Key ConsiderationsDevice types o Screen size and resolution (DPI)

o CPU performance, memory and storage spaceo Development toolso Special needs (GPS or camera, for example)

Network constraints o Occasional connections and/or low bandwidtho Choose protocols based on speed and power consumption

UI design o Delightful user experienceo Different screen sizes of deviceso Security - access, authentication

Architecture o Web app or native app or hybrido Multi-layered architecture

Device constraints o Battery life, memory size, processor speed

WEB APP VS. NATIVE APP VS. HYBRID

Server Processing

No Video

Little OS Integration

No Camera

Online Mode

Easy Distribution

Extensive Reach

High Portability

Geo-location

Camera

OS Integration

Video

Unique Distribution

Limited Reach

Browser-Free

Zero Portability

Offline Mode

Manageable and Rich UX

Online and Offline

Web App Native AppHybrid App

9

ProEasy distribution and update

One version for browsers and mobile devices

Less expensive to develop – shorter time-to-market

Monetize via traditional web monetization, e.g., ads, membership fees, …

Easy way to start into mobile development

ConCannot use device-specific features, e.g., camera

Cannot handle heavy graphics

Must be connected to internet to access

Manage own payment system

WEB APP - PROS AND CONS

10

ProFully integrated with mobile device – can be more efficient

Can use full mobile device features, e.g., camera

Rich graphical experience

Can be used in offline mode

Monetized and distributed via app store

ConDevelopment costs higher if supporting multiple platforms (each platform developed separately although cross-platform development environments exist)

App store approval process

Updates via app store (pull rather than push)

NATIVE APP – PROS AND CONS

11

ProIntegrated with mobile device

Can use full mobile device features, e.g., camera

Online and offline mode

Monetized and distributed through app store

ConGraphics rendered through browser, not native

Development costs higher than web app if on multiple mobile platforms

App store approval process

Updated through app store (pull vs push)

HYBRID APP – PROS AND CONS

TIME TO CROSS ALL PLATFORMS

HTML5 Feature iOSSafari

Android Browser

Chrome BlackberryBrowser

Windows Phone IE

Geo-location

Canvas

Audio

Video

Touch Events

Cache

Web Storage

Web Sockets

Server-Sent

CSS Transition

Web Notifications

HTML5 FEATURES

14BEST USES FOR EACH MOBILE APP TYPE

Mobile App Type Recommended Best UsesWeb App o Business-focused apps that do not need to access mobile

device features, e.g., camerao 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 GamesHybrid App o Apps that require a moderate graphic interface

o Apps that require use of mobile device features, e.g., camera

Many mobile app vendors build both web and native apps.

15

CASE STUDY

ClientLeading provider of fully integrated photo processing solutions and social media services for digital photo labs, commercial printers and fulfillment centers

Business needLarge European client required solution with an integrated mobile client for photo processing and ordering

Did not have resources or expertise to develop mobile app

ResultsDeveloped mobile client for iOS and Android platforms

Initial product released 9-2011

CASE STUDY – RETAIL NATIVE APP 16

CASE STUDY - DEVELOPMENT CHALLENGES 17

Challenge Key ConsiderationsDevelopment technology choiceo Framework vs Native OS

o Chose to work with SDKs of native OS platformso Multi-threading not available at the time on framework client wanted

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 use

Multiple platform developmento iOS Androido SmartPhones, Tablets

o Chose to work with SDKs of native OS platformso Multi-threading not available at the time on framework client wanted

to useSmartPhone vs Tablet form factor

o Look and feel tailored to each form factor (what works on Tablet may not be suitable for SmartPhone)

Internationalization/ Localization

o Look and feel, language support, forms of addresses, …

On-going support of mobile apps

o Keeping up with updates to OS versionso Compatibility testing

CASE STUDY – MOBILE CLIENT

Crop Im

age

Shopping Cart Flow

Select images

Edit Image

s

Key FeaturesOrder processing and image processing

Select images to process or take a picture from mobile camera

Crop images, rotate images, compose multi images

See image on the 3D object (cup, T-shirt, mouse pad,…)

19SUMMARY: WEB, NATIVE, OR HYBRID

Remember: This is not just a technical question.

Key considerationsPurpose of mobile app

Features of mobile app

Distribution and monetization of mobile app

Time to market

Development cost

Development technologies vs development skills

Consider all of the above first and then choose:

Web, Native or Hybrid.

20

QUESTIONS?

Follow-Up Webinars:Consideration When Extending Software Into Mobile, November 28th

www.CorSource.com800.545.6375

419 SW Eleventh AvenueSuite 300Portland, Oregon 97205

155 Bovet RoadSuite 308San Mateo, California 94402

Presented by:

THANK YOU Eileen Boergereboerger@corsource.com

CorSource Technology provides consulting, software development services and technical staffing that businesses need to succeed in the fast-moving, highly competitive world

of software development and IT. CorSource provides services to SMBs and ISVs nationwide. Learn more at

www.corsource.com, and follow us on Twitter: @corsource.