The document discusses standardization gaps in developing and deploying cross-platform native and web apps. It notes challenges in areas like user experience, expenses, device APIs, and security across different platforms. The document compares options like native, hybrid, and web apps, noting tradeoffs in areas like code reuse and platform support. It proposes using frameworks to help address gaps, and describes the Mootwin framework as providing features across platforms at lower cost while reducing complexity and improving performance over other options.

1. What standardization gaps do you see in the market around
development and deployment of cross-platform native and/or web
apps ?
Does that pose challenges and how are you addressing those
challenges ?

2. Q1 2012 Status
Native Hybrid Web
User experience
Rich function
Expenses
Device APIs
Signal Management
Flexible security
Platform Range
Agility
Worst 2
Best

3. Native or Web ?
Gartner : By 2015, half of the applications that today would be written as native mobile apps will be
delivered as mobile Web apps.

4. Native HTML5
Cross platform language &
No Yes
IDE
Code pooling No Yes
Standardized No Yes (2014)
Back-end connect. Any JSON
Performances High Bowser
Market places Yes No
Approval process iOS No
Per
UI Native
platform
4

5. Business
Back-end
3rd party
UI
back-end
Native
Facebook
Application
BL
Twitter
Any other
service
Business
Back-end
3rd party
back-end
BL
UI
Facebook
Web
Web
server
Application
UI
Twitter
User interface
BL Business logic
Any other
service
5

6. How to fill in the gap ?
Using Framework !

7. Source Orange
7

8. PhoneGap Titanium
Javascript
Architecture Native wrapper
runtime
Coding HTML 5 Pure Javascript
Titanium
Renderer Native browser
engine
Native UI No Yes
Market submission Yes Yes
Performances Browser Closer to native
Platform supported 7 2
Plugins Yes Yes (complex)
Complexity Simple More complex
8

9. Native AD toolsets and runtimes
MEAPs with prepackaged apps
There is no perfect solution MCAPs, AD tools with web support
Native
Each one has advantages and
Cost / Complexity
Web
JavaScript and RIA frameworks
weaknesses
Web adapter/transcoding tools
Complexity and performances
Smartphone-optimized site
means heavy tools
Do nothing — rely 100% on web
Quality of User Experience

10. How Mootwin helps reducing the gap between
all the tools and the standards ?

11. Complexity / Mootwin Framework
Performances
Native App
Titanium App
PhoneGap
Wrapper & JS
framework
Web Apps
11

12. Mootwin
App
UI
Weak network
proof
Real time channel
Incremental Mootwin App
cache
Platform
All back-ends BL
Connct.
Certified
Back-end
banking grade
Facebook
Any other
back-end
3rd party
Business
Twitter
service
security
Data query
engine
12

13. Server Side
Mootwin Operation Server
Mobile Side Serveur-side
Enterprise Backend systems
Application Code
Device system
M-Data Exchange
Application Code
M-Data Exchange
M-Identity Management
M-Web Portal
Local Cache (Offline)
Unified PUSH Notif. API
PUSH Notification
Usage Tracking
Runtime Skinning Mobile WebApp
Live Update
13

14. • Strong features & modules for all platforms
at the lowest cost
• Server flexibility & remote management
• Reduction up to 70% of a new platform
development
14

15. Thank you
Emmanuel HAVET
@mootwin
www.mootwin.com
Slides link on Twitter account

16. Mootwin Application Platform
Pro-active M-Identity Multichannel
Context Aware Management
Bi-directional realtime Seamless Interconnection
communication Manage multi-device with backend systems
channel mobile Identity (CRM)
Realtime tracking of Total control thanks to a
Mapping IS Identity and Common & Server-side
users navigation Mobile Identity Business Logic
context
Multi-platform support
User context (phone Multicriteria Filtering (SmartPhone, Tablet,
sensors, location) WebTV, …)
Groups of mobile users
Proactive data pre- In-App Push with rich
based on business rules content
fetching
16

17. Information
System
Accounts
Server-side App
XML Financial
Connector
Data
M-Data Push
001010101100
001010101010 M-Data
Connector Connector
Exchange Engine
Third-Party
RSS
Provider
Connector
News
Provider
Incremental Push updates to • Optimized connector selection
Hides the complexity of connectivity dramatically reduce data exchange et depdending on incoming mobile
and data management to developers increase responsiveness. request
Server-side Cache to optimize backend • Standard connectors for a
Makes transactions fast, secure and
response time seamless interconnection
reliable
(HTTP, REST, SOAP, XML, JSON, …)
Mobile requests mutualization to
Transparent Persistent Offline Storage reduced workload on interconnected • Built-in aggregation mecanism for
17 17
backends multiple datasources