From finance, technology and implementation track at QCon London 2013

1. Consumerisation –
what does it mean to a developer?
Chris Swan
@cpswan

2. Why me?

3. Agenda
• Strategy
• Consumerisation
• Users
• Containers
• Frameworks
• Desktop
• Wrap up

4. Strategy

5. Tactical
Choices Purchasing
= When Decisions
= Who
Operational
Implementation
Details
Details
= How
= What
blog.gardeviance.org/2012/09/whats-my-it-strategy.html

6. Why?
• To give people what they want
– Why do they want these things?
• Travel weight
• Endurance
• Collaborative experience
• Cool factor
– Don’t let this be dismissed as ‘executive jewellery’

7. Consumerisation

9. Enterprise doesn’t choose stuff
People do
Some of those people work for
Enterprise

10. Users

11. Who are the users?

12. Don’t let things get too complex
(and try not to let Conway’s law take hold)

13. User profiles
13

14. Users vs things you care about
14

15. How - Controls
15

16. Who - Ownership
16

17. What – Application Distribution
17

18. Etc.
18

19. Containers

20. Frameworks and Containers -
Overview
Frameworks
Web Hybrid Native
(HTML5)
Container
20

21. Why have a container?
Everything else
Everything else
Everything else
Stuff you care about
(=== local state)
Container
Everything else
Everything else

22. Containers enforce policy
• Authentication
• Encryption
• Key management
Stuff you care about • Network connectivity
• Jailbreak detection
Container • Remote wipe
• Etc.

23. Mobile device management (MDM)
• The device is the container
Container
• This is how things have worked in the Enterprise
PC world for many years. So many people are
comfortable with the model.

24. Mobile application management (MAM)
• The application is the container
Container
• This is relatively new, and hence a little scary.

25. MDM and MAM aren’t mutually exclusive
Container
Container

26. MAM can be multi tenant
Container Container Container
Container

27. And diverse
Container Container Container
Container Container Container

28. And connected
Container Container Container
Container Container Container

29. MAM vs MDM
29

30. Frameworks

31. Frameworks and Containers –
Overview (Redux)
Frameworks
Web Hybrid Native
(HTML5)
Container
31

32. Framework characteristics
Web Hybrid Native
Cross platform Yes Yes No
Local state Limited Yes Yes
(offline capable)
Access camera, GPS & No Yes Yes
accelerometers
Dev tools HTML5/CSS/JS Mostly HTML5/CSS/JS Various (Java,
[1] Objective C, etc.)
'Shiny'[2] Good Better Best
Performance OK OK Optimal
[1] NB Hybrid development still requires platform specific development effort for
each platform targeted, and should not be considered an easy/default option
[2] 'Shiny' is used to describe the look and feel of applications relative to embedded
or exemplar applications on a given platform
32

33. Can HTML5 ever be enough?
The YES camp The NO camp

34. Can HTML5 ever be enough?
The don’t seem to care camp

35. This is not a hybrid strategy
xkcd.com/1174/

36. There is another way

37. Frameworks and Containers – full Picture
Mobile SDK
In house container
Thin client
Web Hybrid Native 3rd party
enabled
(HTML5) apps
legacy apps
Commercial MAM
Web SDK
37

38. Desktop

39. IE sucks!
• Or at least the versions that most banks and
other (large) financial services companies
have on their desktop.
• This does not encourage an HTML5
everywhere approach.

40. A Chromebook diversion
• HMTL5 mostly
• NaCl takes up the
slack
– SSH
– RDP
– Games?
• Seems like a toy?

41. Chromium to the rescue

42. Wrap up

43. Users’ why drives the
who, what, how and when
43

44. Use a container to enforce policy
Everything else
Everything else
Everything else
Stuff you care about
(=== local state)
Container
Everything else
Everything else

45. Choose frameworks to suit use cases
Web Hybrid Native
(HTML5)
45

46. The jury is still out
46

47. Thanks for listening
Are there any questions?