Gizmox provides solutions for building data-intensive apps with HTML5. There is a debate around developing native mobile apps vs HTML5 apps. Native apps set the high bar for user experience (UX) across 7 key dimensions: performance, distribution, look and feel, offline functionality, device integration, push notifications, and real-time data updates. An enterprise HTML5 platform should make it easy to deliver native-quality UX for most business app scenarios by optimizing for performance, supporting various distribution options, enabling adaptive designs, integrating device capabilities, and allowing real-time data and offline functionality. Gizmox argues their platform can quickly bring existing business apps to mobile with native UX using HTML5 and companies' existing

1. Building Native-Quality
Mobile Apps with HTML5
Itzik Spitzen, CTO Josh Epstein, VP Marketing

2. Some Context

3. Gizmox Corporate Overview
FOUNDED: 2007
TEAM: Experienced technologists: HTML5, development
tools, high reliability, compiler tech
Enterprise IT: ex-Microsoft, Oracle, EMC
Tech entrepreneurs
LOCATIONS: US (Cambridge, MA) and Israel
PARTNERS
& CUSTOMERS: Customers: Global 2K Enterprises and ISVs
Partners: Network of VARs and Sis
Strategic: Microsoft and Citrix
Since inception, Gizmox has offered solutions for
building data-intensive apps with rich UIs,
optimized for browser client delivery

4. Gizmox HTML5!

5. vs.
The Great Debate

6. Enterprises are investing heavily in different
approaches to mobilize business apps
develop
native
develop
HTML5
replacewith
outofthebox
virtualize
desktop/app
NOT a debate

7. develop
native
develop
HTML5
replacewith
outofthebox
virtualize
desktop/app
what about user experience?

8. develop
native
develop
HTML5
replacewith
outofthebox
virtualize
desktop/app
what about user experience?
Native apps set the bar for highest
level of UX

9. What does
native-quality
mean?

10. 7 Dimensions
of mobile app
User Experience that
really matter

11. Performance and
Responsiveness
§ Time to render
§ Time to display
§ Time to interact
§ Data updates
§ Control responsiveness /
Touch responsiveness

12. Distribution
§ Monetization strategy
§ iOS/Android Store
§ Enterprise App Store
§ Access from URL
Available on your
Enterprise App Store

13. Look and Feel
§ Themes/
Iconography
§ Control Behavior
§ Screen-screen
flow

14. Offline Function
§ How long will app need
to function offline?
§ What functionality will
need to be available?
§ How much data will be
collected / updated
while offline
!

15. Device Integration
Accelerometer Video Capture Compass Connection Contacts
Camera Device Info Device Events Globalization Notifications
Audio Capture Media Files Local Storage Web Storage File Mgmt

16. Push Notifications
§ Push notifications from
app
Don’t forget about
push notifications

17. Real-time Data Updates
§ Web not designed for
realtime updates
§ Workarounds (e.g.
comet) typically not
mobile-friendly
§ WebSockets changes
the game

18. What should you expect
from an enterprise
HTML5 platform?

19. HTML5 applications can deliver native-quality user
experiences for a large portion of business app
scenarios. Choose a platform that makes this easy.
Performance and
Responsiveness
Make strategic use of javascript,
performance-optimized platform
Distribution
Decide your preferred strategy.
Leverage Hybrid approach for
distribution via store.
Look and Feel
Use adaptive design concepts to
built themed skins for your app
for use on different devices
Device Integration
Built Hybrid app with PhoneGap
or other hybrid wrapper
Push Notifications
Develop into your app directly or
leverage MBaaS offering
Real Time Data
Leverage WebSockets to maintain
persistent connection with server
side processesOffline
Use client-side javascript and
offline storage and back-to-sync
capability to ensure seamless
recovery from offline events
!

20. Get your business apps to enterprise-class HTML5
quickly, securely, with your existing development team.

21. Bring your apps to mobile with native-quality HTML5
quickly, securely, with your existing development team.

22. 23
Thanks for your time.
Q&A