The consumer is spoilt for choice. Most of the buzz is around apps that individuals consume. Why? Because apps are sexy, provide unique experiences. Consumer discover new things to do, or new ways of doing existing things. Many are now billion $ brands with global recognition. Take Facebook, which has seen meteoric growth since it embraced mobile. But there is another market, which frequently gets overlooked. This market is: - Not sexy - Not looking for unique experiences - Has its own unique set of challenges. But this market has 1 unique characteristic: It has in-built buyers. Who am I talking about? The employees! The global workforce is 3 Billion. The white collar workers are tech savvy, well educated, already using consumer level apps on their own mobile devices. How does this make them a captive audience? The magic word: Apps for the Enterprise. Reality Check: Nearly 3/4th of the enterprises have built less than 5 apps, of which 40% is at 0-1 app only for their employees. According to Gartner, by 2017, 25% of all enterprises will have app stores. Companies will invest in HTML5/Hybrid apps to fulfill demand from employees for apps. Why should developers go for it? The market is growing. A Nasscom report says the Enterprise Mobility market is expected to be worth $140 Billion by 2020. What about enterprises? - People bring own devices, clamor for support from companies - IT no longer controls budget, biz units are recognizing a need for such initiatives and building their own apps - Biz units bypass corporate guidelines in order to access data faster & collaborate more effectively Unfortunately businesses fail at building effective apps.Most apps are the result of squeezing a web app onto a mobile device. Companies need to focus on 5% principle. A mobile app will have only 5% features of the web app, but features that drive the most value. How to become Mobile First? Use Business Architecture approach 1. Identify your stakeholders 2. Map your current & potential modes of engagements with stakeholders 3. Evaluate the engagements vis-a-vis business strategy 4. Identify capabilities required to support these engagements 5. Cost/benefit analysis of building new engagements Mobile Maturity Lifecycle: - Opportunistic: No central mobile strategy, one off mobile projects - Strategic: Strategy varies by business unit, development tools & resources in place, but not optimized for scale - Mobile First: Central strategy tied to business metrics, IT governance balanced with business data needs, scalable development methodology Key Challenges to Mobility: Supporting employee devices, managing security, configuring new & legacy systems, go native/hybrid, managing pvt app stores BaaS - An alternative to mobile middleware. Complexity of building a backend can be time consuming & expensive. By de-cluttering the backend of app development, developers can focus on the user experience and the app itself.

1. When
Elephants
Dance:
Enterprise
goes
Mobile
Abhay
Aggarwal
Principal,
Mobility

2. The journey of a man…

3. THIS
IS
AN
EXAMPLE
OF
A
LONG
PRESENTATION
SECTION
HEADING
Not just a Smartphone…anymore

4. THIS
IS
AN
EXAMPLE
OF
A
LONG
PRESENTATION
SECTION
HEADING
10 Million…and counting

5. THIS
IS
AN
EXAMPLE
OF
A
LONG
PRESENTATION
SECTION
HEADING
Consumer is KING

6. THIS
IS
AN
EXAMPLE
OF
A
LONG
PRESENTATION
SECTION
HEADING
What’s in it for developers?

7. THIS
IS
AN
EXAMPLE
OF
A
LONG
PRESENTATION
SECTION
HEADING
There’s another market out there

8. THIS
IS
AN
EXAMPLE
OF
A
LONG
PRESENTATION
SECTION
HEADING
Who is Buying?

9. THIS
IS
AN
EXAMPLE
OF
A
LONG
PRESENTATION
SECTION
HEADING
What’s the Magic Word?

10. THIS
IS
AN
EXAMPLE
OF
A
LONG
PRESENTATION
SECTION
HEADING
1 in 4 enterprises
will have app stores

11. THIS
IS
AN
EXAMPLE
OF
A
LONG
PRESENTATION
SECTION
HEADING
Why should developers go for it?

12. THIS
IS
AN
EXAMPLE
OF
A
LONG
PRESENTATION
SECTION
HEADING
B2E is RISING

13. THIS
IS
AN
EXAMPLE
OF
A
LONG
PRESENTATION
SECTION
HEADING

14. THIS
IS
AN
EXAMPLE
OF
A
LONG
PRESENTATION
SECTION
HEADING
It’s a Marathon

15. THIS
IS
AN
EXAMPLE
OF
A
LONG
PRESENTATION
SECTION
HEADING
Why Mobile First?

16. Failure to build an effective app

17. Becoming Mobile First

18. Becoming Mobile First
Identify Stakeholders
Map engagements
Evaluate engagements against strategy
Identify capabilities
Cost/Benefit analysis

19. Mobile Maturity Life Cycle

20. Mobile Maturity Life Cycle
OpportunisFc
Mobile
Strategic
Mobile
Mobile
First

21. Key Challenges to Mobility

22. Key Challenges to Mobility
BYOD
Security
Backend Services
Legacy Infrastructure
New Infrastructure
Native/Hybrid?
Enterprise App Store

23. Evolution of the Ecosystem

24. Backend
as a
Service

25. Backend
as a
Service
Data Store
REST API
Optimized DataTransfers
User Management
Communication
Social
Geo location
Analytics

26. Why Use
BaaS?

27. In Summary

28. • BYOD
is
driving
consumerizaFon
in
IT
in
enterprise
• MarkeFng
now
controls
the
purses;
not
IT
• Ini?al
adopters
in
Sales
force
automaFon,
CRM,
Field
Service
AutomaFon
• Companies
are
grappling
with
how
to
build.
Real
Ques?on
should
be
What
to
build?
• Remember
the
5%
rule
• BaaS
de-­‐cluGers
the
backend,
so
that
developers
can
focus
on
experiences
• Open
source
will
leapfrog
proprietary
plaKorms
• Begin
with
Cost
saving
models
&
graduate
to
Revenue
generaFng
models

29. ONE LAST THING

31. An
army
travels
on
its
stomach.
Napoleon Bonaparte

32. aaggarwal@xebia.com
www.xebia.in

33. References
Mobile Stats
• http://mobithinking.com/mobile-marketing-tools/latest-mobile-stats
Enterprise Mobility
• http://www.wired.com/insights/2013/02/why-your-enterprise-must-rethink-mobile-
app-development/
• http://www.wired.com/insights/2013/08/enterprise-mobile-apps-old-school-new-rules/
• http://www.mobilemarketer.com/
• http://mobileenterprise.edgl.com/top-stories
BaaS
• http://en.wikipedia.org/wiki/Backend_as_a_service
• http://blogs.forrester.com/michael_facemire/12-04-25-
mobile_backend_as_a_service_the_new_lightweight_middleware
• Google & Flickr Images