AJAX for Mobile Devices - 04/2009

AJAX for Mobile Devices
Using Apache Projects to get the job done
Roland Tritsch
Director PS FUSE
ACCU 2009 - Apr., 23rd - Oxford (UK)

© 2009 Progress Software Corporation
2
Why is this relevant?
 “The only bright spot in the PC industry is netbooks. Analysts at the Gartner
research company said shipments rose to 4.4 million devices in the third quarter
of 2008, from 500,000 units in the first quarter of last year. Analysts say sales
could double this year despite a deep worldwide recession.” - NYT -
26/01/2009
 “According to new research from CompassIntelligence.com, businesses in the
US will spend roughly $11.6 billion on mobile applications by 2012. ...
<snip> ...The highly mobile Healthcare industry is expected to spend an
estimated $1.1 billion on mobile applications by 2012, although the Government
and Services industries are expected to be the top spenders on mobile
applications.” - Compass Intelligence - 04/09/2008
 “An iPhone record: 500 million App Store downloads” - Apple - 16/01/2009
 Internet usage on mobile devices has dramatically increased since 2007. This
proliferation is the result of a rapid increase in processor power, improvements in
network connectivity and reductions in the costs of mobile computing. Many
mobile devices now include the same or similar Web browsing software as
desktop computers. As a consequence, mobile device users expect access
to the World Wide Web anytime, anywhere and from any device. -
MobileAjax - 2008
“Mobile is the next Desktop!”

3
Why is this relevant?
 “The only bright spot in the PC industry is netbooks. Analysts at the Gartner
research company said shipments rose to 4.4 million devices in the third quarter
of 2008, from 500,000 units in the first quarter of last year. Analysts say sales
could double this year despite a deep worldwide recession.” - NYT -
26/01/2009
 “According to new research from CompassIntelligence.com, businesses in the
US will spend roughly $11.6 billion on mobile applications by 2012. ...
<snip> ...The highly mobile Healthcare industry is expected to spend an
estimated $1.1 billion on mobile applications by 2012, although the Government
and Services industries are expected to be the top spenders on mobile
applications.” - Compass Intelligence - 04/09/2008
 “An iPhone record: 500 million App Store downloads” - Apple - 16/01/2009
 Internet usage on mobile devices has dramatically increased since 2007. This
proliferation is the result of a rapid increase in processor power, improvements in
network connectivity and reductions in the costs of mobile computing. Many
mobile devices now include the same or similar Web browsing software as
desktop computers. As a consequence, mobile device users expect access
to the World Wide Web anytime, anywhere and from any device. -
MobileAjax - 2008
“Mobile is the next Desktop!”
Developing solutions for the
mobile platform will more and
more become part of the
everyday software engineering
challenge!

4
This talk ...
 Build and maintain distributed (mobile)
applications/systems and minimize the cost
doing it
 A key cost factor are people
• Ramping up a skill and/or have them use a skill
 You need to A&D systems that are “easy” to
build and maintain
• AST - Architecture, Standard, Tools
• A&D and Code
... is also about money!

5
What are the options?
 Go Native ...
• iPhone SDK (Objective-C), Windows Mobile
(C++), Symbian (C++), Palm (C++),
Blackberry (C++), Android (C++)
• High cost, very good results
 Use Java ...
• CLDC/MIDP, CDC, AGUI, OSGi, lots of JSRs
• Medium cost, good results
 Use the Browser (and AJAX :)) ...
• Internet Explorer, Safari, Firefox, Opera
• Low cost, maybe “good enough” results
One way to look at it ... (the “if-you-have-to” approach)

6
The Project(s) ...
 Mobile Health Care Solution
• To make patient data available to doctors and
nurses, while they provide home-care services
• Cutting costs in the health care system and
increase traffic on the mobile network
 Mobile Payment Solution
• Use mobile devices to make “cheque” like
payments between businesses and individuals
• Use a widest possible variety of devices
... that were driving some of the research!

7
Agenda
 Why is this relevant?
 Characteristics of a Mobile-SOA Platform
• Comparing the available approaches
 Using AJAX to get the job done
• Introducing AJAX and some relevant Apache
Projects
 Summary, Wrap Up and Q&A
• The “Sensoric” Revolution

8
What makes “Mobile” special?
 Limited Hardware
• Limited Screen “Real Estate”
• Limited CPU, main memory, disk space
 Limited Network Connectivity
• Limited Bandwidth
• Unreliable Network Connectivity
 The Application Design
• Offline vs. Online
• Request/Response vs. Fire-and-Forget
• Short- vs. Long-Running
The client side hardware/the devices!

9
“Mobile” A&D requirements
 Design for maximum battery life
• No constant looping/heavy CPU usage
• No polling
• DOM/XML parsing is expensive
– consider JSON
 Design for minimum data traffic
• Both for performance and cost
• “Chunk” the data/interactions to ensure
“responsive” user experience
 Design for maximum device portability
• Testing is key

10
Consider the application
 “On Device” Mobile Application
• e.g. Game - lots of computing, not a lot of web
access/traffic
 “True” Mobile Web Application - less
computing, but lots of interactions with lots of
services
• EMail, Twitter, ..., Online Banking - large
number TXs, but (hopefully) small size of TX
 Behavior ...
• short interrupt driven, expect fast reaction,
“explore” (desktop) vs. “focused” (mobile)
Categories, behavior, ...

11
What are the options (revisted)?
 Go Native ...
• iPhone SDK (Objective-C), Windows Mobile
(C++), Symbian (C++), Palm (C++),
Blackberry (C++), Android (C++)
• High cost, very good results
 Use Java ...
• CLDC/MIDP, CDC, AGUI, OSGi, lots of JSRs
• Medium cost, good results
 Use the Browser (and AJAX :)) ...
• Internet Explorer, Safari, Firefox, Opera
• Low cost, maybe “good enough” results
One way to look at it ... (the “if-you-have-to” approach)

12
Agenda
Projects

13
The “1-Slide” AJAX Tutorial :)
 Asynchronous JavaScript and XML (AJAX)
• Coined by James Garret [2005]
 Based on ...
• JavaScript, DOM (HTML/XML) and
XMLHttpRequest
 Allows for interactive, partial, req/resp-style
updates/refreshes of web-pages/content
 Famous use-cases ...
• Google-Suggestions
• DART-Tracker (at least for me :))
Background and Concepts ...

14
... a sequence diagram ...
Source: www.modelworks.com

15
<a onClick=”onClickSayHi()”>Say Hi!</a>
---
function onClickSayHi() {
var xmlHttpRequest = GetXmlHttpRequestObject();
// setup anonymous callback function to deal with response
xmlHttp.onreadystatechange = function() {
if(xmlHttp.readyState != 4) return;
// LOTS of unmarshaling code goes here
}
// LOTS of marshaling code goes here
xmlHttp.open("GET", url, true);
xmlHttp.send(null);
}
... and some source code :).

16
The browser “maze” ...
 Opera Mini - Presto
 (Apple/iPhone) Safari - Webkit
 (Google) Android - Webkit
 Nokia (s60) - Webkit
 Access Netfront - Netfront
 (RIM) Blackberry - Mango
 (Palm) Blazer - Netfront
 (MS-Windows Mobile) Internet Explorer
... and how to navigate it.

17
Mobile AJAX “challenges” ...
 Hidden server interaction creates a risk for
the user experience
• Ensure UI behavior is in sync with network
behavior
 DOM/XML marshaling must be managed
• To manage CPU and battery
 Services wrapping required
• for Technologies - e.g. CORBA to HTTP/XML
• for Semantics - Distributed to Mobile
 Limited access to device features
• No solution - consider JAVA, Native
... and how to overcome them.

Using Apache Projects to get the job done
 Server-side SOA platform
• Apache ServiceMix, ActiveMQ,
CXF
 Server-side service wrapping is
required
 But what to do about the client
side ... ?
18

Using Apache CXF to access the Mobile SOA
 Java-Script generation
capabilities
• wsdl2js, ...?js URL extension
• supports SOAP, XML, JSON
 Very simple API
• onSuccess(), onError(), ...
 “Eliminates” marshaling code
 No “installation” needed
 Source Code/Podcast
• www.tritsch.org - Podcast
19

20
Agenda
Projects

21
Resources to consider ...
 http://www.apache.org - SMX, AMQ, CXF
 http://www.openajax.org - Mobile AJAX TF
 http://www.youtube.com - Demystify AJAX
 http://www.w3schools.com - AJAX, DOM
... in case you want to learn more.

22
Summary/Conclusions
 Given the right requirements, using AJAX is a
viable approach to build mobile applications/
solutions
 You still need to wrap the services :)
 Apache open source projects can help you to
build a/the Mobile SOA platform

23
Questions

24
Questions
Thank You!

25

AJAX for Mobile Devices - 04/2009

More Related Content

What's hot (20)

Viewers also liked (8)

Similar to AJAX for Mobile Devices - 04/2009 (20)

More from Roland Tritsch (6)

AJAX for Mobile Devices - 04/2009