going mobile: choosing target devices & platforms
DESCRIPTION
A process for making a key early mobile development decision: which platform/technology to choose.TRANSCRIPT
going mobilechoosing target devices & platforms
Barbara Ballardhttp://www.littlespringsdesign.com
development options
iMode
SMS
MMSmessaging web
app multiapp native
widgets x15
XHTML Basic
XHTML MP
WML
Java ME
Flash LiteSVG
mojax (etc.)
ECMAScript “web”
picture
Palm
Symbian
Linux QTARM
Windows Mobile
UIQ
IM
BREW
data sync
typical thinking
“Let’s design for the RAZR”
“Let’s design for the RAZR”
“Our market is all phones”
“It’s gotta work on iPhone”
“Let’s design for the RAZR”
“Our market is all phones”
“Smart phones are key”
“It’s gotta work on iPhone”
“Java is a nightmare”
“Java is the best answer”
needs-based thinking
a selection methodology
• class of technology based on application & user needs
• native, cross-device app, web, messaging
• specifics of technology based on market, distribution, and internal company needs
• Java, BREW, web, scripting, Symbian, etc.
mobile needs come from
• users & context
• distribution: on/off deck; market
• device & platform capabilities
• necessary application behavior
• data needs
• the carry principle
the carry principlea user’s mobile phone is always carried
fashion statement
reflection of personality
battery powered
multipurpose
small screen
specializedpersonal device
1 handed operation
inconsistent connectivity
difficult text entry
communications focus
device proliferation
application & user needs
interaction needs
• reliability of data access
• interaction flow
• glanceability of data
• freshness of data
• interaction richness
data access reliability
messaging web
app multiapp native
present unless device
lost
present unless device
lost
only when data access
could be
delayed roamingair travel
coverage hole
calendarcontacts
search
interaction flow
messaging web
app multiapp nativeexcellent good
slowvery slow
script only somewhat supported
action games
call contact
add to calendar
news
glanceability of data
• single screen paradigm makes difficult
• browser, app not likely running• less true for smart phones
• smart phone home screens
• future: widgets
freshness of data
messaging web
app multiapp native
excellentgood
RSS
contacts
stocks
takes effort
takes effort
interaction richness
messaging web
app multiapp native
moderatescarce RSS
turn by turn directions
stock qoutes
rich good
script only somewhat supported
action games
device feature access limited
business needs
• Business users - mostly “smart phones”• North America: Windows Mobile, Blackberry
• Europe: Symbian, some Windows
• Asia: mix - Linux, ARM
• Consumers - mostly “feature phones”• Africa: Symbian, Windows
• elsewhere: mix (Symbian uncommon in US, Asia)
target market = devices
impact of device selection
messaging web
app multiapp native
limited to“smart phones”
wide -“feature phones”
XHTML - wide
script - narrow
text - all
other - wide
smart phone?
named OS?
downloadnativeapps?
heavydata
distribution issues• carrier (“on deck”)
• only way to distribute BREW
• off deck• may need carrier relationship anyhow
• SMS links• disabled by Verizon
• 3rd party sales (e.g., Handango)
discovery issues• environmental (e.g., billboard)
• camera input/MMS
• short codes
• messaging apps
• downloadable apps (carriers may block)
• URL
• .mobi unnecessary (m.gmail.com)
• on deck
platform issues
web issues
• limited script support
• variable standards
• Opera Mini vs. Mobile
• helper apps
• Flash Litemessaging web
app multiapp native
messaging issues
• SMS ubiquitous
• no guaranteed delivery
• lag
• MMS rendering differences
• premium SMS costlymessaging web
app multiapp native
native app issues
• expensive to maintain
• 6% market in US
• highest data use
• still rendering issues
• less supported by carriersmessaging web
app multiapp native
multi-device platform issues
• BREW via carrier only
• rendering issues
• device support varies
• launch times (esp. Java)
• testing & portingmessaging web
app multiapp native
mobile development
SMS
MMS
widgets x15
XHTML BasicXHTML MP
WML
Java ME
Flash Lite
SVG
mojax (etc.)
ECMAScript
“web”picture
PalmSymbianLinux
QT
ARMWindows Mobile
UIQ
IM
BREWdata sync
iMode
Barbara Ballardhttp://www.littlespringsdesign.com