IBM MobileFirst begins with a mindset: Innovative enterprises see the opportunities gained by bringing all resources together to strengthen customer engagement–whenever and wherever the customer wants, and on the customer's favorite device, which is often mobile. Whether transforming your customer acquisition strategies, streamlining your business process, or boosting product and service innovations, you can accomplish more by focusing on mobile computing environments first. IBM MobileFirst offers you true end-to-end mobile solutions. Some providers specialize in service offerings; some focus on platform and application development; some offer only mobile security; while others focus just on mobile device management. We bring it all. We help your customers initiate transactions at the moment of awareness. You can encourage customer-building touchpoints and deepen relationships with your customers with realtime, one-to-one engagements. Learn what they want with powerful mobile analytics and usage data, then create more compelling interactions. We can also help you increase workforce productivity through mobile apps that enhance collaboration, improve knowledge sharing, and speed responses. Gain efficiency by extending existing business capabilities and applications to mobile workers, partners, and customers.

1. IBM MobileFirst
HYBRID APP DEVELOPEMENT

2. WHY WE WILL BEAT THE COMPETITION What’s in it for you?
1
we can easily reuse and leverage on your existing
investments (infrastructure, solutions, ... )
2
we provide a secure solution and security
best practices out-of-the-box
3
Most of all, currently Worklight is considered the best
solution (technically, functionally, architecturally)

3. LITTLE INFO ABOUT ME
Wim Tobback
@wimtobback
WHO’S THIS GUY?
I’m the IBM Enthusiast @ Cronos
§ Started in 2004 (01-04)
§ IBM Solution Architect
§ Living near Leuven
§ Born 31-01-1982

4. Worklight Whaat?
/Despicable me
IBM Acquisition
§
§
§
On 31-01-2012
For about $70M
Israel
Worklight
§ An open, comprehensive and advanced mobile application
platform
§ That assists you to efficiently develop, run, and manage HTML5,
hybrid, and native applications
§ using standards-based technologies and tools
§ mobile-optimized middleware
§ a variety of security mechanisms
§ integrated management and analytics capabilities.

5. Worklight Gartner Magic Quadrant for Mobile Application Development Platforms

6. Worklight Why?
APPS
30%
Cross-Platform development
and testing
Security
Offline sync
Geo-fencing
Direct Updates
Integration
Push Notifications
…
70%
Mobile
Application Platform

7. Worklight Different Components – The architecture

8. Worklight Different Components – The architecture
The Worklight Studio
§
§
§
§
§
Eclipse Based IDE (Plugins)
Native, hybrid and standard web
Dojo, jQuery, Sencha,…
Device SDK integration
Supports auto-complete and
validation

9. Worklight Different Components – The architecture
The Worklight Studio
§ Eclipse perspective
§ Optimized layout for hybrid
app development
§ Rich page editor: drag-anddrop, palette of components,
properties view, beautified
outline, and raw editable
source code
§ Changes to code
automatically apparent in
rich page editor, and viceversa, for quick development
Support for
DOJO and
Jquery Mobile

10. Worklight Different Components – The architecture
The Worklight Studio
§ Common code is placed in a primary
location
§ Environments optimizations allow
overrides to the common code
§ Worklight optimizes the delivery
and merge of the various
environments

11. Worklight Different Components – The architecture
Rich Mobile Simulator
§ Perform device specific tests in the
Mobile Browser Simulator, during
development.
§ Change device types, orientation,
device settings (GPS loc, compass,
etc…)
§ Supports Cordova and Worklight
client API

12. Worklight Different Components – The architecture
The Worklight Runtime
Client APIs available for
both pure native as well
as hybrid development
Extensive libraries and client APIs that expose and interface with
native device functionality and the Worklight server
§
§
§
§
§
§
Cross-Platform Compatibility Layer
Server Integration Framework
Encrypted Storage
Offline Authentication
Runtime Skinning
Statistics and Diagnostics Reporting

13. Worklight Different Components – The architecture
The Worklight Server
A middleware component which delivers unified notifications, version management, security features,
and integration Services
§ Distribution of mobile web apps
§ Enterprise connectivity:
§ Secure client/server connectivity
§ Direct access to enterprise back-end data and transaction capabilities
§ Authentication enforcement
§ Client control:
§ Application version management and remote disabling
§ Direct update of application code
§ Unified Push Notifications
§ Aggregation of usage statistics

14. Worklight Different Components – The architecture
The Worklight Console
Operational management for
§ Deployments
§ Version enforcement
§ Infrastructure access
§ Remote disabling
§ Push Notifications
Operational analytics provide real-time
insight into application usage
§ Data export to BI enterprise systems

15. Worklight Different Components – The architecture
The Worklight Application Center
A cross-platform private mobile
application store focused on the needs
of a development organization or a team

16. Worklight The perfect fit into your existing enterprise infrastructure!
From the complexity of many…
To the simplicity of one
§ Multiple sets of back-end integrations to build and
manage
§ YOU manage caching, authentication and single sign-on,
service interruptions and push notifications
• One adapter per resource
• Worklight Server manages caching, authentication and single
sign-on, service interruptions and push notifications

17. Worklight Connect mobile apps to ALL your back-end services
Adapter Framework
§
§
§
§
§
§
Secure communication
XML-based declarative specification
Multi-source data mashups
Simplified adapter testing
Server-side debugging
HTTP, JDBC, Web services and WebSphere
CastIron integration,…
§ Access to session data and user
properties

18. Mobile Test Workbench for Worklight OUT-OF-THE-BOX!
§ Create, run, and automate tests
§ Improve quality and time-tovalue with industry-first app
testing
§ Comprehensive – Android and iOS,
Native and hybrid
§ Complete – Recording, editing,
and running on mobile devices
§ Resilient – Same test runs
across multiple devices
§ Also for non-developers –
Scripts in natural language
description

19. Securing your mobile Enterprise The challenge
Application Security Design:
§ Develop secure mobile apps using best practices
§ Code obfuscation
§ Encrypted local storage for data
§ Offline user access
§ Challenge response on startup
§ App authenticity validation
§ Enforcement of organizational security policies and standards

20. MARKET DEMAND Mobile Challenges
§ Maintaining the applications with bug fixes, support of new devices and OS updates, ensuring
that content is up to date,…
§ Keeping the apps up to date when backend platform, external service APIs and other
integration points change
§ Updating content from a myriad of content management systems, back office tools and
admin interfaces
§ Learn and reuse from other applications
§ Listening to user feedback on the app stores (Private/Public) and update the apps to
keep users satisfied and engaged
§ Keep consistency of brand and look and feel
§ Securing data on devices, in transit and on server, managing user authentication,
traceability where logging is important

21. So what should you do? Making your mobile apps manageable
As originally stated by Gartner…
“
any organization planning on creating 3 or more enterprise class apps in the
coming years should consider establishing a standardized Mobile Enterprise
Application Platform (MEAP).
“
Short term it may require a bit more work and investment but the investment will
quickly pay off with:
§
§
§
§
§
Faster speed to market and ease of keeping the applications up to date
Lower cost of development and maintenance
Enhanced business intelligence
Data and user security
Other benefits such as brand consistency, change management and System architecture (e.g.
Adapters)

22. Native, Hybrid or Web Different approaches
Hybrid
Mobile Browser
Native Container
Native Container
Native Container
Web Code
Web Code
Web
Native Code
Native Code
Device APIs
Web Code
Device APIs
Device APIs
Native

23. Native, Hybrid or Web Different approaches
Many organizations taking their first steps to implement a mobile strategy are
facing important decisions that will influence the results of this initiative.
The process of choosing a development approach for a mobile application
entails many parameters, such as budget, project timeframe, target audience
and app functionality.
Each approach carries inherent benefits and limitations, and finding the one
that best addresses the organization’s needs is a challenging task.

24. Native, Hybrid or Web Different approaches
Apple iOS
Android
Blackberry OS
Windows Phone
Languages
Objective-C, C, C++
Java (some C, C++)
Java
C#, VB.NET and more
Tools
Xcode
Android SDK
BB Java Eclipse Plug-in
Visual Studio, Windows
Phone development tools
Packaging
Format
.app
.apk
.cod
.xap
App Stores
Apple App Store
Google Play
Blackberry App World
Windows Phone
Marketplace

25. Native, Hybrid or Web Different approaches
The hybrid approach combines native development with web
technology.
Using this approach, developers write significant portions of
their application in cross-platform web technologies, while
maintaining direct access to native APIs when required.
One language, one tool!

26. Native, Hybrid or Web Different approaches
Feature
Pure
mobile
web
apps
Pure
mobile
websites
Tools
and
knowledge
Written entirely in HTML, CSS and
JavaScript
Written entirely in HTML, CSS and
JavaScript
Execution
“Installed” shortcut, launched like a
native app
Reached by navigating to a website by
way of a URL
User
experience
Touch-friendly, interactive UI
Navigational UI between pages
displaying static data
Performance
UI logic resides locally, making the app
responsive and accessible offline
All code executed from a server,
resulting in network-dependent
performance

27. IBIZZ Software Services for Mobile
Understand existing mobile
vision and challenges
Discover business goals
and mobile requirements
Position IBM industry
knowledge and MobileFirst
capabilities
Identify mobile scenarios
and use cases
Define mobile Journey next
steps
Map to IBM MobileFirst
solution portfolio
Analyze key business and
technical aspects of
solution design and
architecture
Define Implementation
Roadmap
Review existing Technical
Environment
Capture (non-)functional
requirements for a given
mobile scenario
Capture user interface and
user experience
requirements
Create functional and
infrastructure solution
design and architecture
Define an actionable
implementation plan
Accelerate adoption by
delivering a tangible mobile
solution to the business in 10
weeks or less
Well defined scope to
progress quickly
Iterative solution delivery
approach including iteration
demos
Implement initial mobile
solution
Deploy solution to pilot users
Recommend next steps
towards Full MobileFirst
implementation

28. Contact me Your next step…
Wim Tobback
@wimtobback
Get connected
§ Twitter : @wimtobback
§ LinkedIn : http://www.linkedin.com/in/wimtobback
§ LinkedIn: http://www.linkedin.com/groups/IBM-WorklightUser-Group-4292377/about
§ Mobile : +32496 11 11 40
§ E-mail : wim.tobback@cronos.be