This presentation gives you an overview about Enterprise Mobility and how that is beneficial for the real time scenarios

1. Enterprise
Mobility
Strategy
• by YUVARAJ ILANGOVAN

2. 2

3. 3
• What do you mean by Mobility?
• The notion of “Mobility” refers
 Mobile Devices –
Smart Phones, Tablets,
Phablets, PDCs, etc.,
 Network Services –
Voice and Data
 Mobility Services --
 Mobile Device Management (MDM) – like securing device, etc.,
 Mobile Application Management (MAM) – Tools, Apps installation, security and compliances
 Mobile Enterprise Application Platform (MEAP) – A solution for developing mobile applications for multi-device
and multi-platforms
• Network
Services
• Mobility
Services
• Mobile
devices

4.  Factors which trigger the need for Enterprise Mobility
COPE – Corporate Owned, Personally Enabled | BYOD – Bring Your Own Device
4
• Why Enterprise Mobility(EM)?
Increased
use of
Mobility by
consumers
Increased use
of Mobility
by
employees
Boom of
COPE / BYOD
policies

5. • Few predictions about Enterprise Mobility
 According to GARTNER, smart phones penetration among
enterprise workforce would be 64% by 2015 and 2/3rd of
workforce will adopt BYOD model
Even 72% of Indian enterprises will improve
productivity by adopting smart phones in everyday
work culture
Per CISCO, “Mobile data traffic grew 81% in 2013 and
expecting that mobile data transactions will be
exploding to 190 Exabytes in 2018”
Per Global Industry Analysts, “Global market for
Enterprise Mobility will exceed U.S$168.8 Billion by
2015”
Per Zinnov, “Enterprise mobility market is expected to
increase almost 5 folds, touching USD 1 Bn by mid-
2015, up from USD 244Mn in 2011”
5
According to IDC, Enterprise Mobility Market
Expected To Touch $1.8B By 2017
• Few leading IT research firms predictions:

6. Reduction in end user IT
cost
Improved employee
productivity, availability
and increase in revenue
Agility in decision making All business reports are
handy and less or zero
paper work (for ex: cloud
printing)
Real time business data
accessibility from
wherever we are
BYOD (Bring Your Own
Device) Policy and it’s
advantages
6
• Benefits of Enterprise Mobility
Enterprise
Mobility

7. Due to fast changes in
mobile landscape, testing
aspects will have lot of
rework and need right
strategy &
implementation for
automation
Device Management and
support for multiple
devices
Rapid pace of change in
mobile hardware OS
landscape
Complexities involved in
terms of data access
policies (COPE / BYOD
policies)
Data security and
compliance maturity and
related issues
Developing and
supporting multiple
mobile OS platforms
7
• Challenges of Enterprise Mobility
Enterprise
Mobility

8. Mobility Terms Problems Solutions
8
Mobile Device
Management (MDM)
 Diversified mobile devices
 Security Implementation
 Remote over-the-air updates
 Prevent malicious software
 Choose mobile devices which has best
possible control and security built-in.
Periodic inventory registry updates
 Have a better security policy with
proper encryptions, locking strategies
(even for mobile’s local storage)
 Identify scenarios like jail-breaks, lost
devices, device theft, repeated login
failures - enable those devices for
remote wiping, automatic padlocking,
account locks, etc.,
 Prepare application white-list and
allow installations for those softwares
only
 Proper SSL, VPN implementations
 New security updates and patches for
diversified platform devices
 Deploy intrusion detection and
prevention systems (IPS / IDS)
• Mobility Challenges and Solutions

9. Mobility Terms Problems Solutions
9
Mobile Application
Management (MAM)
 Acquiring apps
 Distribution of apps (discovery)
 Security
 Tracking & Support
 Enterprise App Store - Improve mobile
worker productivity by giving them
easy access to the apps they need
through an enterprise app store
 App Management – Using Enterprise
App store, companies will get
following benefits:
i) Deploy, monitor and support
ii) Prepare apps white / black list
to prevent app malwares
iii) Complete control on apps
towards security &
compliance
iv) Data protection and
management
• Mobility Challenges and Solutions [Contd…]

10. • Mobility Challenges and Solutions [Contd…]
List of industry leading MDM /
MAM Tools
• Airwatch Enterprise Mobility Management
• BlackBerry Enterprise Service 10
• BoxTone (acquired by Good Technologies)
• XenMobile
• Good for Enterprise
• IBM Endpoint Manager for EM
•MaaS360
•MobileIron
• SAP Enterprise Store
•MobiControl
• Symantec mobile management suite
• Apperian
10

11. 11
• Types of mobile app development
Native Apps
Mobile App
Types
Cross
Compiled
Custom
Container
Mobile Web
Hybrid
Apps

12. • Mobile application types and their capabilities
Device Features Native Hybrid Mobile Web
GPS High High High
Accelerometer High Medium Medium
Camera High High Not Accessible
Gyroscope High Low Not Accessible
3D Graphics High Low Low
Bluetooth High Low Not Accessible
Device Information High Low Not Accessible
SMS High Medium Not Accessible
Local Notifications High Medium Not Accessible
Local Database High Medium Low
Push Notifications High Medium Not Accessible
Contacts Details High Medium Not Accessible
Calendar High Medium Not Accessible
12

13. • Decision making factors for Mobile App Development
Decision Factors
End user and the platform
App Features (heavy use of gestures, animations, device features, etc.,)
Product Usage / App Traffic
1. Are you expecting your product will be used heavily?
2. What would be the approximate number of users ?
Time and Budget for Development due to platform
proliferation
1. How many platforms should be supported?
2. How many form factors should be supported?
3. Skilled developers (Native vs Web)
Discoverability of App
Write Once Use / Optimize Everywhere
Security (Native is better than Mobile Web)
Network Bandwidth (GPRS, 2G, 3G, Wi-Fi)
13

14. • Decision making factors for Mobile App Development
14
General queries
before making right
strategy for Mobile
App Development
• Which platform that we need to target for app development (iOS, Android,
WinMo, RIM)?
• Should our EM solution be native / hybrid / mobile web?
• Do we need to build app from scratch or can use any of existing Mobile
Enterprise Application Program (MEAP) framework solutions?
• Should organization provide devices (COPE) or employees can bring their
devices (BYOD)? In any case, do we have right policies and compliances for
Mobile Device Management (MDM) and Mobile Application Management
(MAM)?
• How about the device and data security implementations?
• How the corporate app should be distributed for employees usage?

15. • When to choose specific development approach
Development Type Scenarios
15
Native
Choose:
Need for specific platforms like iOS, Android, RIM, Windows
Want to develop app based on devices features. For ex: SKYPE
 Need to have rich UI and high responsiveness performance based apps
 Apps can be used even in offline mode
 In a nutshell, if we want to develop more consumer focused app with cutting
edge features, fluid animations and graphics, fast performance and security then
Native app would be the right choice
NOT to choose:
If the app development is targeting multiple platforms, versioning and
maintenance will be difficult in future
 We should have skilled developers for native programming
 Publishing app is a detailed process (like AppStore) and it would be really difficult
if the app doesn’t support the standards defined

16. • When to choose specific development approach
Development Type Scenarios
16
MobileWeb
Choose:
If we need “Write once, run every where” model, Mobile Web would be
the choice
Same code base that can be accessed from multiple devices, multiple
platforms and browsers.
You can leverage your existing web developers with no or minimum
training for the development
If you want to enhance the user experience for existing web sites, Mobile web
version of the site would be an easy option as it’s SEO friendly and mainly faster
development time
NOT to choose:
 If the app requires access of specific device features
 If the app requires heavy graphics and animations

17. • When to choose specific development approach
Development Type Scenarios
17
Hybrid
Choose:
 When your app requires to be accessed everywhere, from multiple devices and
should have capabilities to access device features
 If you have faster time-to-market scenarios, Hybrid development and market cycle
would be faster than Native apps
 If your app requires all web features and good UX experience, this is the right
option
 Development, deployment and maintenance would be easier compared to Native
apps
NOT to choose:
 Due to extra layer, you can experience slightly lower performance with
UI rendering and data access
 Compared to Mobile Web, this approach will require separate wrappers should be
developed for each platform and this may increase the development, deployment
and maintenance duration

18. • Mobile App Development Tools – An overview
Apple (iOS) Android BlackBerry Windows Phone
Language Objective C, Swift JAVA (C++) JAVA C#.Net, VB.Net
Tools XCode Android SDK BB Java Eclipse
18
Native Development Tools
Mobile Web Development Tools (Few Notable names)
 Jquery Mobile
 Sencha Touch
 Worklight
 Twitter’s Bootstrap
Plug-in
Visual Studio, Windows
Phone SDK
Packaging .app .apk .cod .xap
Publishing App Store Google Play App World Marketplace

19. • Mobile App Development Tools – An overview
Hybrid App Development Tools (Few Notable names)
19
 PhoneGap
 Appcelerator Titanium
 Xamarin
 Orubase
 AppMobi
 RhoMobile
 Corona

20. • Enterprise Mobility – Reference Conceptual Architecture Model
20

21. • Enterprise Mobility – Logical Architecture Model
21

22. • Mobile Middleware in Enterprise Mobility
•Updating the changes in applications (hosted in AppStore,
etc.,)
• Messaging and Notification services (SMS, Push
Notifications, etc.,)
• Brokering for application integrations (For ex: back-end
integration)
• Device detection and experience adaptation
• Location APIs (to support location based apps)
• Asset transcoding (converting image, sound, video to
Mobile supported formats)
• Mobile specific analytics (like apps crashing metrics, etc.,)
• Capacity offload (hosted caching layers for high
performance mobile interactions)
• Application security (like apps data wipes, application
access, selective encryptions)
Functionalities that
offered by Mobile
Middleware (part of
MEAP):
22

23. • Mobile Middleware in Enterprise Mobility
23

24. 24
What problems are solved
by Mobile Cloud (MC)?
• Separate the actual data
(storage issues) from mobile
device
• Separate the data processing
(computing overheads) away
from mobile device
• As the data and computing
part is off-loaded to MC,
mobile devices will be left with
resources overhead free (like
battery life, processing power,
etc.,)
Current challenges in
Mobile Cloud
• Network connectivity
• Long WAN latency
• Mobility management
• Context-processing
• Vendor / Data lock-in
• Security / Privacy
• Mobile Cloud in Enterprise Mobility

25. 25
• Mobile Cloud in Enterprise Mobility

26. Thank You !!!
26