The document discusses strategies for architecting mobile solutions for enterprises. It covers pillars of a mobile strategy including defining a strategy, development costs, and focusing on audiences. It also discusses mobile sites versus native applications, highlighting tradeoffs between the two approaches. Mobile sites can be built using HTML5 and jQuery Mobile to work across platforms with progressive enhancement. Native applications require developing for specific platforms like iOS and Android. Cross-platform frameworks like PhoneGap can help develop native apps using HTML5.

1. 24th July 2013
Sachin Bhosale
Architecting Mobile Solutions for
the Enterprise

2. Contents
Introduction
Pillars of Mobile Strategy
Mobile Sites vs. Native Applications
Mobile Sites
• Mobile Architecture
• Building Mobile Websites
• HTML5 and JQuery Mobile
Mobile Applications
• Patterns of Mobile Application Development
• Cross Platform development

3. Introduction - The World Is Going Mobile
 Over 50% of the world’s households carry a
mobile device – 3B+
 Global mobile traffic now represents roughly
13% of Internet traffic.
 In India, mobile internet traffic surpassed
desktop internet usage in May 2012 – other
countries to follow
 Out of 4B+ mobile users, 1B+ are
smartphone users.
The future is already here – it’s just not evenly distributed

4. Pillars of a Mobile Strategy
• Define a Mobile
Strategy
• Development and
Costs
Going Mobile
• Focus on your
audience
• Delivery Models
Outlining a
B2C Strategy • Serve your (limited)
audience
• Mobile Enterprise
Application Platforms
Outlining B2B
Strategy

5. Mobile Sites vs. Native Applications
Server side solution
One Site Fits (almost) All
Hassle Free Deployments
No Access to Hardware
capabilities
Varied Browser Capabilities
Network Latency
Fast and fully integrated
App Store Integration
User Experience
Isolated Mobile Continents
(iOS, Android etc.)
Minimized SEO
Mobile Sites
Native Applications

6. Mobile Sites > Architecture
o Stereotypes to refresh
o Analysis first
o Defining a Mobile Application Layer
o Server-Side Device Detection
o Multi serving
o One Web
• People Don’t Like
Mobile Sites: Why
Bother?
• You Don’t Need
Mobile Sites at All
• A Tiny HTML Page Will
Do the Trick
• One Site Fits All
Myths

7. Mobile Sites > Building Mobile Sites
o Application Structure
o Single Page Interface (SPI) Model
o Full Page Refresh
o Partial Page Refresh
o The Device Detector Site
o Routing to mobile views
o Detecting device capabilities
o Putting the site up

8. Mobile Sites > HTML5 and jQuery Mobile
o jQuery mobile is a cross-platform UI
framework for creating webapps for
touch-enabled smartphones and
tablets
o non intrusive semantic HTML5 code
o open sourced & lightweight
o multi platform with progressive
enhancement
o build one site that works on any
browser
o Supports almost all platforms

9. Mobile Applications
• A applications developed to run natively on the targeted device, usually
written in a device specific language like Objective-C or Java.
• Delivered through App stores
 To achieve a significant market adoption, your solution needs to target at
least 4-5 platforms:
iPhone , Android, Blackberry, Windows Mobile, Symbian too
 Are you going to engineer for all?

10. Mobile Applications > Interaction Patterns
o Back and Save Pattern
Save the content of input screens when the user leaves (or is forced to
leave) the screen
o Guess-Don’t-Ask Pattern
Use any available resources to make intelligent guesses and save users the
largest possible bit of interaction
o A-la-Carte-Menu Pattern
o Sink-or-Async Pattern
Implement asynchronously any operations expected to perform for longer
than a bunch of ms
o Logon-and-Forget Pattern

11. Mobile Applications > Presentation Patterns
o Babel-Tower Pattern
Avoid hard-coded and fixed layout text and design your application to
support the dynamic injection of properly translated text.
o Do-as-Romans-Do Pattern
It is compelling for users, and possibly also advantageous for developers,
to abide by the look and feel and capabilities of the host operating
system.
o List-and-Scroll Pattern
Don’t be afraid of using (vertical) lists in your mobile application, even
long lists that contain more than 100 items to scroll.

12. Mobile Applications > Behavioral Patterns
o Predictive Fetch Pattern
If you depend on network connectivity, download data that is likely to be
used later and make sure you have enough data stored at any time to
survive a lack of connectivity.
o Memento-Mori Pattern
Applications always should save their relevant state when the operating
system forces them into the background.
o As-soon-as-Possible Pattern
Remote operations that are critical for the application should be
implemented in a protected manner and reiterated a few times before
failing. In case of failure, however, the operation should be recorded and
played back as connectivity returns.

13. Mobile Applications > Cross platform development
The Virtual Machine Approach
A virtual machine is an environment that creates a sort of abstraction layer
on top of some underlying hardware
The Shell Approach
The idea behind the Shell approach is to integrate a web-view native
component with the user interface of the application
 Titanium Mobile
 Flash Builder

14. Mobile Applications > Developing with PhoneGap
PhoneGap is built around a very simple
(but effective) idea: you build a local
HTML5 application, and the framework
packages it as a native application for a
variety of mobile platforms

15. Thank you!