1) The document discusses technologies that can enable enterprises to become mobile-first, including mobile device/application management, compelling UI/UX design, and next generation mobile application platforms. 2) It promotes applying an application factory approach using reusable application components to help IT quickly respond to business needs. 3) An ideal next generation platform would provide visibility across the entire mobile application lifecycle and allow integration of best of breed tools through an open ecosystem of developers.

1. Mobile Matters: Technologies to
Enable Mobile First Enterprises
Michael King
Director of Enterprise Strategy
Appcelerator
@mobiledatamike
mking@appcelerator.com

2. Mobile Matters:
Technologies to
Enable Mobile First
Enterprises

3. Agenda
• State of the market
• Technologies to support mobile-first
enterprises
• A lifecycle approach
• Creating an app factory
• Requirements for a next generation
mobile platform

4. State of the market
Massive device fragmentation, first
with Android, now beginning with
Apple
Enterprises has no control over the
devices their customer apps will be
consumed on, and with BYOD, less
control for employee apps
No end to fragmentation in site…

5. Native Development
WEB Separate development teams
iPhone
Different development languages
Different development
SAP environments
Android
Impossible to align delivery
schedules
Oracle Each App must be built 3-4 times
BB
No reusable components
No way to enforce standards of
Social design or governance
Too costly, too time Windows 8
consuming, impossible to sustain

6. HTML5 As the Cure?
WEB
SAP HTML 5
+
CSS
Oracle
Social
Gives you a “write once, run poorly everywhere” experience

7. Traditional Mobile Enterprise
Application Platform Architecture
A new market requires a new approach

9. What We‟ve Heard From Our Clients
Challenges:
We require visibility across the entire Mobile Application Lifecycle:
Plan, Build/connect, Test, Release/Manage, and Analyze
We require connections to multiple backend systems, public networks,
web services and social networks
I can’t train people on all of the studios and development languages required,
and my outsourcing partner doesn’t have the developers/skills I need
I have islands of information about my apps, some in the LOBs, some in the
apps teams, some in testing, and no way to manage all of my apps
The market and LOBs demand rapid application response, I need to enforce
governance, branding standards, and consistent connection methods

10. Agenda
• State of the market
• Technologies to support mobile-first
enterprises
• A lifecycle approach
• Creating an app factory
• Requirements for a next generation
mobile platform

11. Technologies For Mobile-First
• Compelling UI/IX
• Mobile Device
management/Mobile
application management
• Next generation mobile app
platforms

12. Compelling UI/UX
A well designed, compelling app is easier to
learn and easier to use, everyday
If the app focuses on UI and device specific
interactions, it will achieve:
Lower support costs
Reduce training time
Achieve higher adoption
Achieve application goals more rapidly
BYOD (Bring your Own Device) evolves quickly
to Bring Your Own App (BYOA) forcing the
Enterprise to focus on application design and
user centric interfaces even for employee facing
apps!

13. MDM vs MAM
MDM: Mobile Device Management: A device centric
security and management capability, to encrypt, mange
and wipe the entire device
MAM: Mobile Application Management: An application
or data centric method of distribution and securing the
application or solely the data that application uses
Both may be appropriate, depending on regulations,
device ownership, application requirements and
security posture
Can be purchased in a traditional client server model
or hosted/cloud based
Costs range from 3-4 dollars per device per month to
400-500 per device for a perpetual license

14. Next Generation Platform
• It’s not about any device, it’s about all of them,
at anytime
• Consistency of user state across devices,
maintain the applications state, with unique
device-specific functions, views, and look/feel
• Data sources are both owned and public;
ERP, CRM, Social, Web, Maps…
• Sharing of information across applications via
the cloud
• Information flows and permissions are infinite,
based on developer requirements

15. Benefits of a Platform Approach
Transform
Phase
Benefits outweigh Accelerate
cost of platform Phase
Explore
Phase
Zero Apps
Number of Applications

16. Agenda
• State of the market
• Technologies to support mobile-first
enterprises
• A lifecycle approach
• Creating an app factory
• Requirements for a next generation
mobile platform

17. Mobile Application Lifecycle
Analyze Plan
Manage/ Build/Co
Release nnect
Test

18. Mobile App Lifecycle
Execs and Business
App Owners Analysts, Devel
Analyze Plan opers
Manage/ Build/Co
Release nnect
Release and Server and
security Enterprise
managers Test Developers
Functional and
performance
testers

19. Mobile Application Lifecycle
CEO/GM of
“What are my customers doing with these mobile
LoB banking apps?”
LoB App “Show me where all of the all of the apps with have
Owner/VP
Apps/ CMO for our banking customers stand in development
and testing”
Development
“Lets see how the latest increase in productivity of
Management my Titanium team affected the testing queue”
Corporate “I need to know where the app I was working on is
Developer crashing?”

20. Mobile Application Lifecycle
CEO “How many apps do we have? What are they
doing for us?”
“What are the employee apps using, in terms of
CIO
resources and modules?”
“I need to know where every app in our estate
Mobility
CoE / VP stands, in terms of development, testing, and
Mobility production”
Corporate “What happened to the expense management
Developer app I submitted to testing?”

21. Agenda
• State of the market
• Technologies to support mobile-first
enterprises
• A lifecycle approach
• Creating an app factory
• Requirements for a next generation
mobile platform

22. Application factory
• While everyone starts with one
app…
• As enterprise builds multiple
applications, standardization
enables repeatability
• The enterprise will quickly move to
disposable applications
• Each application running on a new
device class is a new application

23. Application Components
Branded elements
(logos, colors, graphical
elements)
Connection to CRM system
Login/password admin
Encryption of data in transit
Developer then „stitches‟
Connection to twitter/facebook the elements of the mobile
application together

24. Next Generation Platform
– Visibility across the entire Mobile Application
Requirements: Lifecycle
• Build, test, deploy, manage, analyze
– Vibrant, involved ecosystem of SIs and
developers to extend the platform
– Standards-based development language and
studio
– Ability to integrate best of breed tools
(MAM, Testing, Bug Reporting)
– Modular capabilities to componentize app
elements for maximum reusability, and
enforcement of standards

25. Appcelerator
Mobile Client Development with Titanium
Appcelerator Mobile Cloud Platform
API
Cloud Storage
API Services
Services Push (Data &
Services (backup
Engine File)
)
Custom Connector Layer
Examples Custom/Leg
acy

26. MEAP vs Next Generation
Next Generation
Advantages
• Scalability
VS • Single development
environment
• Client side
• Server side
• Lower Cost (less upfront
Mobile Client Development with Titanium
investment)
• More Deployment
Appcelerator Mobile Cloud Platform options (VPC, Behind
Cloud API
Servic
es
API
Servic Push
Servic
es
Stora
ge
(Data
Firewall)
Engin es (back
& File)
e up)
Custom Connector Layer

27. Rating Development Options
Traditional Native Traditional MEAP Next Generation
Application Platforms Mobile Application
Approaches Platforms
Enforceable N/A Yes, limited to Yes, fully extensible
standards for supported options through the
application elements ecosystem
Native, Hybrid and N/A No, native or Yes
HTML app support wrapper
Open architecture for N/A No, closed systems Yes
integration of best of
breed
Ecosystem of SI, Yes, depending on SIs but few Open ecosystem
ISVs and developers OS developers/ISVs
Standards-based, N/A Proprietary, In the same
customizable significant additional development
backend connectors costs

28. Mobile Maturity Model

29. Conclusions
• Technologies for the mobile first enterprise
are:
– MDM/MAM
– Next Generation Platforms
– UI/UX
• Application factory Approaches will enable IT
to react quickly to the requests from the LOBs
• Next generation platforms must enable
visibility across the App lifecycle, regardless
of role
• Mobile maturity goals will dictate the pace of
technology investments