Developing the Client Side

Going the Web Way

Going the Web Way: Solutions
• jQuery Mobile;

• Sencha Touch.

2
jQuery Mobile: Overview
• Browser-based mobile application development
framework that sits on top of jQuery;
• DOM-based coding approach to mobile development;
• Supported by Adobe and jQuery Foundation;
• Open Source;
• Relatively good IDE support;
• Compile to native app with PhoneGap.

3
jQuery Mobile: Views

4
jQuery Mobile: Handling Remote Data

5
jQuery Mobile: Development Tools – ThemeRoller
• Browser-based
visual WYSIWYG
designer;
• Does not allow
you to define or
edit event
handlers.

6
jQuery Mobile: Development Tools – Ionic Creator
• Browser-based visual
WYSIWYG designer;
• Does not allow you to
define or edit event
handlers.

7
jQuery Mobile: Conclusion
• Pros:
– Easy DOM-based syntax to master;
– Large numbers of developers already fluent in jQuery.
• Cons:
– No built-in MVC development framework;
– DOM syntax can be repetitive;
– Performance;
– Likely to need 3rd party plugins.
• Best suited for very small projects.

8
Sencha Touch: Overview
• Browser-based mobile application development framework;
• Uses similar development paradigms to Ext JS 4;
• JavaScript MVC class-based approach to development;
• Open source supported by Sencha;
• Compatible with most mobile browsers;
• Compile to native app with either PhoneGap or Sencha
CMD;
• Native API support for some device APIs;
• Excellent developer and code generation tools available.
9
Sencha Touch: Views

10
Sencha Touch: Handling Remote Data

11
Sencha Touch: Development Tools - Architect
• Visual Application
Builder;
• Visual Theme
Builder;
• Code generation
tools;
• Command-line
utility.

12
Sencha Touch: Development Tools - Eclipse
• Consistent code
completion;
• Template creation;
• Integrate with build
and debugger.

13
Sencha Touch: Conclusion
• Pros:
– Full-featured WYSIWYG IDE available;
– Best performing mobile web framework;
– MVC framework well-suited to large development projects;
– Documentation, examples, tutorials.
• Cons:
– Syntax and MVC framework can be challenging to master;
– Performance not as good as native applications.
• Best overall framework for line-of-business and
enterprise application development.
14
Developing the Server Side
REST Resources
REST Resources
• REpresentational State Transfer:
– An architecture style, not a standard;
– HTTP requests to read, create, update or delete data;
– Stateless, lightweight;
– Nouns as URLs, verbs as HTTP methods.
• Resource:
– Identified by at least one URL;
– Can contain sub-resources;
– Exposed through representations.
16
Resource-Oriented Architecture
• Addressability;
• Statelessness;
– No connection state maintained between REST invocations.
• Connectedness:
– Resources should link together in their representations.
• Uniform interface:
– Same set of operations for each resource.

17
REST Implementations
• JAX-RS:
– Jersey;
– RESTEasy;
– RESTlet;
– CXF.
• Spring MVC;
• .NET:
– WCF.
• NodeJS:
– Express.
18
Request Mapping in Jersey

19
Request Mapping in Jersey (II)

20
Request Mapping in Spring MVC

21
Request Mapping in WCF

22
Request Mapping in Express JS

23
Thank you!

24