IBM’s keys to starting mobile development.

GET IN THE

MY SCREEN,

YOUR SCREEN.Size it right.Mobile screens vary widely, so one-size-fits-all…

won’t. Plan accordingly. Pick and choose only the

most essential data to display.

1

2

Once, the keyboard was king. But for mobile,

you’ll have to accommodate a range of user

inputs like voice, location and image, and

gather feedback constantly for updates.

GO NATIVE! OR DON'T.3 ways to implement mobile.You’ve got a few options when it comes to writing the software.

Native: Apps written specifically for one device and OS. Supports

more features but needs more versions.

Web: Apps using code that works on most devices, but lacks

extensive mobile features.

Hybrid: Apps that work across devices—optimized with snippets

of native code.

UX an d i n puts.TAKING IT ALL IN.

DEADLINE?

UM...NOW.Mobile has to be agile.You'll need to collaborate on continuous

build, test, integration and deployment.

Respond rapidly to feedback.

4

TESTING, TESTING ,

1,2,3,4, 5…It’s complicated. But it’s crucial.

5

Get into it!

You’ll find more app-dev guidance in our Mobile Development PrimerYou’ll find more app-dev guidance in our Mobile Development Primer

3

Many testing matrices have thousands of permutations. And

you’ve got to address user experience and feedback, too.

There are three ways to do it:

Manual: Testing the app on every device is invaluable—but

expensive and time-consuming.

Automatic: Running key UX scenarios on a device emulator

is quicker and easier—but less thorough.

Cloud: Testing actual releases on actual devices without

buying them saves you time and money.

MOBILE DEVGAMEMOBILE DEVGAME