Kony-Forrester Webinar: The Evolution of Mobile First Development

Making Leaders Successful Every Day

The Evolution of "Mobile First" Development Jeffrey Hammond, Principal Analyst September 26, 2012

3 Entire contents © 2010 Forrester Research, Inc. All rights reserved.

Source: Flickr (http://www.flickr.com/photos/sashawolff/3793206523/sizes/l/)

9/11 1.3 M+ Android activations per day, 500 million+ total devices 9/12 400 M+ iOS devices sold to date

Mobile is the new face of engagement

Are you ready for the Mobile Shift?

It’s becoming a BYOT world

This creates real differences for IT shops

Devices: Company-provided Employee-owned

Life cycle: Three to four years 12 to 18 months

Applications: Java EE, .NET, Flash Objective C, Java, HTML5, WinRT

Provisioning: IT push App store pull

Security: Locked down Zero-trust

Are you Agile enough?

Do you collect (and incorporate) rapid feedback?

Can you design useful, usable, desirable experiences?

Are you ready?

Can you build high quality, 5 star apps?

Source: Flickr (http://www.flickr.com/photos/kaz25/2444344463/sizes/o/in/photostream//)

Assemble small, focused development teams

•  Plan for smaller teams (3-6), and more of them •  Scrum, and “Scrum of Scrums” are a good starting model •  If you go native specialize developers w/ technology •  Hire design talent, and invest in information architecture •  QA + security is everyone’s job – retire the QA center of

excellence •  APIs everywhere, all the time •  Downsize your sourcing strategies

iOS Dev Team Android Dev Team Web Dev Team

Lead iOS Dev

iOS Dev

Lead Android Dev

Android Dev

Lead Web Dev

Web Dev

Design Team Scrum Master/ProjM Product Owner/PM

Shared, Cross Team Roles

Cross-train Cross-train

Cross-train

Native Apps Argue For Cross Training

Favor simpler ALM processes

•  Fewer branches in SCM – evolve toward DVCS •  Use visual designs and prototypes instead of textual

requirements •  Emulators and On-device testing mean more hands on

developer time •  CI becomes decentralized, more atomic, and critical •  Test like you deploy – the last mile may be public and

beyond your control •  Mocks and mocking tools help manage multi layer

complexity

Systems of Engagement

Building apps changes the dev life cycle

Time to Safety

Time to Certainty

Time to Feedback

Systems of Operation

Systems of Record

Lifecycle Focus

Adapting Agile principles

•  Kanban boards help manage atomic demand •  Use wireframes to drive feedback and build backlog •  Use visual prototypes to gather “broad brush” feedback •  Develop personas to drive insight into user behavior •  Think about “contextual” design •  Employ journey maps to understand multi-channel

usage patterns

Wow

Enjoyable

Functional

Neutral

Missed It

Frustrating

Awareness Consideration Research Purchase Engagement

1

2 3

4 5

6 7 8

9

10

11

Identify customer and

stages of journey

Indicate primary (and secondary ) devices for each step

Describe each step in the journey, the customer’s needs and perceptions

Indicate significant

steps

Persona: James

A Multi-channel Journey Map

Prioritize gathering user feedback

•  Collect feedback early and often •  Assign someone to listen to public feedback •  Analyze feedback for recurring patterns of failure and

opportunity •  Proactively reach out to unhappy users •  Build feedback and analytic systems into your

applications •  Ask for positive reinforcement •  Create a regimen of A/B testing

Balance release speed with a focus on quality

•  Initial quality is important – due to app store curation •  Expedited releases are no substitute for real testing •  “Blue/Green” environments complement A/B testing

approach •  Deployment and feedback management tools grow in

importance •  Simultaneous release across clients is important •  Avoid patches – bundle bugfixes with new features •  Don’t wait for GA – use platform betas •  Moves to organic releases that meet user and market

demands

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

V 1.0 (MVP)

V 1.2.2 V 1.2 V 1.2.1

Regression + Emergency Patch

New OS version released

V 2.0 V 2.1

Features + Defect fixes

Regular Internal Sprint Cycle + Beta Testing (2 weeks)

A Typical Mobile App Release Schedule

Your technology choices matter

Native Web

Middleware

Hybrid

Maximum Performance

Cost Effective

Frequent Updates

Pixel-perfect Experience

A simple guide for technology decisions Think about the workloads you are automating…

Native Web

Middleware

Hybrid

The gaps between strategies are shrinking

Native Web

Middleware

Hybrid

WebGL IndexedDB Device API

Mixed Mode Middleware

On-premises/Private Cloud

Public Cloud

Modern mobile apps: Evolving Infrastructure 3x3 strategies for building mobile apps

Native Web

Hybrid

Roll-your-own Backend BaaS

Middleware Server

Mobile Clients

Service Infrastructure

LDAP/IAM SCM LOB 1 LOB N CRM

Systems of Record

Middleware vs. rolling your own backend

• Labor costs vs. capital costs

• Do you have mixed mobile workloads?

• Is infrastructure control important?

• How cutting edge are your needs?

• How skilled is your development team?

• How complex are your integration needs?

• What testing resources do you have?

• How fast do you need to move?

The future of mobile is context – drop your “mini-PC” mindset now

With new sensors, your phone will know more about you than anyone or anything Consumer demand for convenience will kill privacy

http://www.flickr.com/photos/22320444@N08/4272283260/sizes/m/

BIG MOTHER IS HERE TO HELP

YOU

Opportunities for context will increase Technology Opportunity (examples)

• 3D cameras • Biometrics • Conversational voice recognition • Near Field Communications (NFC)

• Distance measured, gesture control • Security, access cards, ID • Verbal command (e.g., Siri) • Payments, ticketing, and information C

ontr

ols

• 3D displays • High-resolution displays • Micro-mirrors • Touch inputs (fine-tuned)

• Augmented reality, video output • Media consumption, bar codes • Image projection; pico-projectors

Dis

play

s

• Accelerometers (detects motion/tilt) • Chemical sensors • Gyroscopes • Magnetometers • Microbolometers (infrared) • Pressure sensor

• Phone orientation as control, pedometer • CO detection, food freshness • Gesture control, navigation, games • Directions – “Is it over there?” • Night vision; heat; light/dark • Height in buildings

Dat

a co

llect

ion

Source: A.M. Fitzgerald & Associates, Yole Développement, and interviews with Atmel, InvenSense, and Sharp Electronics

Mobile is moving fast – and getting faster •  Mobile devices are the biggest shock to your world

since the introduction of the PC •  Enterprise mobile is collapsing into a consumer based,

BYOT reality – a mobile first reality •  You must push your development organization to get

faster, and more flexible to compete •  You need multiple approaches to support mobile

workloads, and the infrastructure to integrate it •  Do you want to spend your time building

infrastructure, or building apps? •  Mobile context will enable breakthrough experiences –

if you are ready to take advantage of them

Sriram Ramanathan CTO Kony Solutions, Inc.

25 Copyright © 2012 Kony Solu5ons, Inc. CONFIDENTIAL 25

Build Everywhere Run Everywhere

The KonyOne Mul5 Channel PlaLorm

NATIVE SUPPORT FOR 8 OSs

Kony MESSAGING SERVICES

Write Once A single code base

TABLET WEB SUPPORT-‐ Mobile and Desktop •  Individual, device op5mized sites •  Basic HTML >> HTML5

Single Page Architecture

Standard

Mixed Mode

Hybrid

MOBILE

KIOSK & DESKTOP NATIVE Win32 and Win8

DESKTOP WEB HTML 5

HTML 4

26 Copyright © 2012 Kony Solu5ons, Inc. CONFIDENTIAL 26

CHAN

NELS

ON-‐DEVICE APP CONTAINER

KIOSK DESKTOP WEB WIN 32/Win 8 DESKTOP TABLET SMART PHONE FEATURE PHONE

ON-‐DEVICE APP STORE

Cross Channel API

§  UI / UX §  Device Features §  U5lity

Channel Specific ProperOes

§  UI / UX / Widgets §  OS Features

Foreign FuncOon Interface

§  New Device API §  Non – UI §  Third Party Workflow

Connectors

§  Services §  Data Conn §  ERP / CRM

FOUNDA

TION

Device Detec5on Usage & Analy5cs Flow Controller

KonyOne Studio

§  Form Designer §  Script Editor §  Publish / Deploy

KonyOne Server

§  Device Detec5on §  Usage & Analy5cs §  Flow Controller

Kony Sync Server

§  Full Offline Capability

§  Audit Metrics

Kony MAM

§  Console §  Enterprise

App Store

COMPO

NEN

TS

§  Alert Services §  Device Database §  Mobile Web Hos5ng

§  Event Editor §  Service Defini5on §  Data Mapper

Mul5 Channel PlaLorm

Mixed Mode NaOve

iOS

Blackberry Android

Web OS

Windows Phone

Symbian J2ME

Web – Mobile and Desktop

URL Server Based

Hybrid

Single Page Architecture

TECH

NOLO

GIES

Basic HTML

HTML5 §  Mix and match HTML5 and Na5ve code on

form by form basis

§  Leverage na5ve capabili5es and rich HTML5 for fully op5mized apps

§  Create seamless experience for end users

Kony-Forrester Webinar: The Evolution of Mobile First Development

Documents

Transcript of Kony-Forrester Webinar: The Evolution of Mobile First Development