EXTENDING SOFTWARE INTO MOBILEEileen Boerger

President“Key Considerations When Migrating Software to Mobile”

The Opportunity Costs

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

WHY MOBILE?

3

Employees demanding access to enterprise applications via their mobile devices in the office, on the road or at home.

Companies realizing they can leverage an employee’s device to reach organizational goals

BRING YOUR OWN DEVICE (BYOD)

95% of organizations permit employee-owned devices in some way, shape or form in the workplace.

4

Key issues to consider to support BYOD

Secure access – authentication

Data security and integrity - during transfer, on mobile device, in the cloud

Client governance policies – variable and inconsistent

Design for multiple mobile platforms

BYOD CONSIDERATIONS

5

Lessons Learned

Mobile UI is different, and each type of mobile device has different UI requirements.

You don’t have to provide all access from the mobile device, i.e., your mobile apps don’t have to do everything.

Don’t underestimate security implications of going mobile.

Design data access carefully and securely.

An evolutionary approach to delivering mobile access is a good strategy.

A web app is a real choice, i.e., you don’t have to build a native app.

Good enterprise app software developers do not necessarily make good mobile app developers.

MOBILIZING YOUR SOFTWARE PRODUCT

Now is the time to mobilize your software product – before it’s too late!

6KEY PLANNING CONSIDERATIONS

Planning Area Key ConsiderationsMobile 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?

Application workflow o Which part of the application workflow on mobile?o Custom workflow for mobile device?o Custom workflow depending on task on mobile device?

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?o Data security?

Distribution and Monetization

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

7

Deliver key minimum functionality quickly

Information access only

Targeted productivity gains for key roles and tasks

Create a strong user experience

Consider doing a web app vs a native app for the first release

Develop plan that adds/changes mobile app on a periodic basis

Develop mechanism for feedback on mobile app

AN EVOLUTIONARY APPROACH

Strongly consider an evolutionary approach.

8

UI design

Don’t just miniaturize your current UI

Tailor the UI for different devices, different user roles and/or tasks

Consider adding social networking to your mobile software product

Mobile users conditioned to use social networks

Create sense of community of product users

Engage community to enhance product

BE INNOVATIVE!

9KEY 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 Not data intensive – information on demando 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

TIME TO CROSS ALL PLATFORMS

Many mobile app vendors build both web and native apps.

12

CASE STUDIES

13

Problem: Doctors a bottleneck in approval process for patient charts/orders

Need access to laptop to check if approvals needed

Need access to laptop to approve charts/orders

Patient meds or orders might be delayed

CASE STUDY 1 - HEALTHCARE

Limited mobile interface to existing product

14

Solution – Develop mobile app for doctors that notifies and allows approval of patient charts/orders

Native app: iPhone and Android phones

Redesign of UI, including displaying medical charts, patient information in readable form for mobile phone

Incorporated use of text messaging to notify doctor of charts needing approval

Results

Higher productivity for users

Have platform for expanding access to more functionality of software product

CASE STUDY 1 – OVERVIEW AND RESULTS

Client

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

Business need

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

Did not have resources or expertise to develop mobile app

Results

Developed mobile client for iOS and Android platforms

Initial product released 9-2011

CASE STUDY 2 – RETAIL NATIVE APP 15

CASE STUDY 2 - DEVELOPMENT CHALLENGES 16

Challenge ConsiderationsDevelopment Technology ChoiceoFramework 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 use

Device Memory Constraints o Working with several large photos at a timeo Required choosing 32 photos at a time (cropping, page placement,

Caption, Image, etc.)

Multiple Platform DevelopmentoiOS, Androido SmartPhones, Tablets

o iOS 3.x 4.x and now 5 for iphone and ipad o Android for specific devices (Xoom, Samsung, …etc.) Device-specific Android (2.1, 2.2, 3.0, 3.1) Testing of multiple Android devices

Smart Phone 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 Looks and feel, language support, forms of addresses, …etc.

On-going support of mobile apps o Keeping up with updates to OS versions compatibility testing

CASE STUDY 2 – MOBILE CLIENT

Crop Im

age

Shopping Cart Flow

Select images

Edit Image

s

Key Featureso Order processing and image processing

o Select images to process or take a picture from mobile camera

o Crop images, rotate images, compose multi images

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

18SUMMARY: EXTENDING SOFTWARE INTO MOBILE

Start Now!

Key considerations

User roles and functionality on mobile app

Workflow for the mobile app

Data access, security, and integrity

Secure access to mobile app

Development technologies vs development skills

Strongly consider an evolutionary approach

Be innovative

UI design for mobile devices

Social networking

19

QUESTIONS?

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.