WebSphere is a platform for developing mobile apps across different platforms and devices. It allows creating web apps using open web technologies like HTML5 and JavaScript that can run on mobile browsers, as well as hybrid and native mobile apps. WebSphere provides tools for building apps targeting different mobile requirements and capabilities. It also offers server-side capabilities for integrating mobile apps with back-end systems and managing mobile apps across devices and platforms.
Tata AIG General Insurance Company - Insurer Innovation Award 2024
WebSphere as a platform for mobile apps
1. WebSphere as a platform
for mobile apps
Henrik Sjöstrand
WebSphere Technical Sales
IBM Software Group, Sweden
henrik@se.ibm.com
2.
3. JavaScript Frameworks for Rich Internet Applications
IBM invests in the Dojo framework. Why Dojo?
• Open source project
• Comprehensive feature set
• Commercial-friendly licensing
• Globalization and accessibility support (WAI-ARIA)
• Well architected
http://dojotoolkit.org/ • Active user community
Alternatives: jQuery, YUI, Ext JS, MooTools, Prototype, script.aculo.us, DWR and others...
but often more targeted at spicing up a web page
5. Mobile: Different Approach for Different Requirements
Web Mobile Web Hybrid Mobile Native Mobile
Application Application Application Application
Characteristics
Desktop and mobile using open Mobile only using open web Mobile only, app runs on the Mobile only, developed using
web (HTML, JavaScript) client (HTML5, JavaScript) client device, but leverages open web native languages or transcode
programming models programming models (HTML5, JS) via JavaScript to native via MAP tools
bridge
Limited to no device-specific Off-line capabilities Native appearance and
functionality Native device capabilities device capabilities, performance
(GPS, camera, contacts)
Mimic native appearance
Mobile Browser Execution AppStore download and install
Traditional Trade-offs
(without MEAP/MAP)
Richness of Mobile Presentation / Services
Portability (cross-device reuse)
Maintenance Cost (TCO)
5
6. Mobile: Different Approach for Different Requirements
Web Mobile Web Hybrid Mobile Native Mobile
Application Application Application Application
a,
Characteristics
v t
native languages or a
Desktop and mobile using open Mobile only using open web Mobile only, app runs on the Mobile only, developed using
web (HTML, JavaScript) client (HTML5, JavaScript) client device, but leverages open web
to native via ,
J transcode
h
programming models programming models (HTML5, JS) via JavaScript
bridge
+ ig
+ MAPLtools
Limited to no device-specific
functionality
Off-line capabilities
Native device capabilities
(GPS, camera, contacts)
/C lver
Native appearance and
device capabilities, performance
C i
Mimic native appearance S
Mobile Browser Execution AppStore download and install
Traditional Trade-offs
(without MEAP/MAP)
Richness of Mobile Presentation / Services
Portability (cross-device reuse)
Maintenance Cost (TCO)
6
7. Mobile: Different Approach for Different Requirements
Web Mobile Web Hybrid Mobile Native Mobile
Application Application Application Application
a,
Characteristics
+
Desktop and mobile using open Mobile only using open web Mobile only, app runs on the
native languages or a
v t
Mobile only, developed using
L
web (HTML, JavaScript) client (HTML5, JavaScript) client device, but leverages open web
to native via ,
J transcode
ig
h
M jo
programming models programming models (HTML5, JS) via JavaScript
bridge
+ + MAPLtools
HT Do /C lver
Limited to no device-specific Off-line capabilities Native appearance and
functionality Native device capabilities device capabilities, performance
(GPS, camera, contacts) C i
Mimic native appearance S
Mobile Browser Execution AppStore download and install
Traditional Trade-offs
(without MEAP/MAP)
Richness of Mobile Presentation / Services
Portability (cross-device reuse)
Maintenance Cost (TCO)
7
8. Mobile: Different Approach for Different Requirements
Web Mobile Web Hybrid Mobile Native Mobile
Application Application Application Application
a,
Characteristics
+
Desktop and mobile using open
5 ile
+
Mobile only using open web Mobile only, app runs on the
native languages or a
v t
Mobile only, developed using
L
web (HTML, JavaScript) client
L
(HTML5, JavaScript) client device, but leverages open web
to native via ,
J transcode
h
M jo M ob ig
programming models programming models (HTML5, JS) via JavaScript
bridge
+ + MAPLtools
HT Do HT jo M /C lver
Limited to no device-specific Off-line capabilities Native appearance and
functionality Native device capabilities device capabilities, performance
(GPS, camera, contacts) C i
Do S
Mimic native appearance
Mobile Browser Execution AppStore download and install
Traditional Trade-offs
(without MEAP/MAP)
Richness of Mobile Presentation / Services
Portability (cross-device reuse)
Maintenance Cost (TCO)
8
9. dojox.mobile widgets (iPhone & Android themes)
Heading with a back button Round Rectangle List Round Rectangle List Edge-to-Edge List
(Variable Height)
Edge-To-Edge List List with Buttons Tab Container Edge-To-Edge List
in a Tab
11. 1
1
Web 2.0 & Mobile Feature Pack for WebSphere
With WAS V6.1 & 7.0
Web 2.0 Web Web 2.0 OSGi Apps Java
EJB 3.0 Services
CEA XML SCA
& Mobile & Mobile & JPA 2.0 Batch
J2EE 1.4 WAS V6.1 Web Java EE 5
EJB 3.0 Services WAS V7
With WAS V8
Web 2.0 & Mobile Dynamic Scripting
CEA XML SCA
OSGi Apps Java Java EE 6 WAS V8
& JPA 2.0 Batch
No additional cost. Supported by IBM.
13. Mobile: Different Approach for Different Requirements
Web Mobile Web Hybrid Mobile Native Mobile
Application Application Application Application
a,
Characteristics
+
Desktop and mobile using open
5 ile
+
Mobile only using open web Mobile only, app runs on the
native languages or a
v t
Mobile only, developed using
L
web (HTML, JavaScript) client
L
(HTML5, JavaScript) client device, but leverages open web
to native via ,
J transcode
h
M jo M ob ig
programming models programming models (HTML5, JS) via JavaScript
bridge
+ + MAPLtools
HT Do HT jo M /C lver
Limited to no device-specific Off-line capabilities Native appearance and
functionality Native device capabilities device capabilities, performance
(GPS, camera, contacts) C i
Do S
Mimic native appearance
Mobile Browser Execution AppStore download and install
Traditional Trade-offs
(without MEAP/MAP)
Richness of Mobile Presentation / Services
Portability (cross-device reuse)
Maintenance Cost (TCO)
13
14. Mobile: Different Approach for Different Requirements
Web Mobile Web Hybrid Mobile Native Mobile
Application Application Application Application
a,
Characteristics
+
Desktop and mobile using open
5 ile
+
Mobile only using open web +
5 ile
Mobile only, app runs on the
native languages or a
v t
Mobile only, developed using
L
web (HTML, JavaScript) client
L
(HTML5, JavaScript) client
L
device, but leverages open web
Mbridgeob a
(HTML5, JS) via JavaScriptp to native via ,
J transcode
h
M jo M ob ig
programming models programming models
+ MAPLtools
HT Do
Limited to no device-specific
functionality HT jo M
Off-line capabilities HT jo M neG
Native device capabilities
+
/C lver
Native appearance and
device capabilities, performance
C i
Do Pho
(GPS, camera, contacts)
Do S
Mimic native appearance
+
Mobile Browser Execution AppStore download and install
Traditional Trade-offs
(without MEAP/MAP)
Richness of Mobile Presentation / Services
Portability (cross-device reuse)
Maintenance Cost (TCO)
14