Consumerization - What Does It Mean to a Developer?
•
0 gostou•904 visualizações
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1ajQT4e. Chris Swan discusses user experience for banking and financial mobile applications, architectures, and the frameworks and containers that ease the way to secure deployment into production.Filmed at qconlondon.com. Chris Swan is a strategist, architect and advisor who has spent the last 12 years working at the boundary of emerging technology and financial services. Lately he's concentrated on cloud, security and mobile technology, and the business value that can be found at the intersections of those topics. Twitter: @cpswan
Recomendados
Mais conteúdo relacionado
Destaque
Destaque (14)
Mais de C4Media
Mais de C4Media (20)
Último
Último (20)
Consumerization - What Does It Mean to a Developer?
- 1. Consumerisation – what does it mean to a developer? 5883 Chris Swan @cpswan
- 2. InfoQ.com: News & Community Site • 750,000 unique visitors/month • Published in 4 languages (English, Chinese, Japanese and Brazilian Portuguese) • Post content from our QCon conferences • News 15-20 / week • Articles 3-4 / week • Presentations (videos) 12-15 / week • Interviews 2-3 / week • Books 1 / month Watch the video with slide synchronization on InfoQ.com! http://www.infoq.com/presentations /UX-mobile-consumerization
- 3. Presented at QCon London www.qconlondon.com Purpose of QCon - to empower software development by facilitating the spread of knowledge and innovation Strategy - practitioner-driven conference designed for YOU: influencers of change and innovation in your teams - speakers and topics driving the evolution and innovation - connecting and catalyzing the influencers and innovators Highlights - attended by more than 12,000 delegates since 2007 - held in 9 cities worldwide
- 4. Why me?
- 5. Agenda • Strategy • Consumerisation • Users • Containers • Frameworks • Desktop • Wrap up
- 6. Strategy
- 7. Tactical Choices = When Purchasing Decisions = Who Implementation Details = What Operational Details = How blog.gardeviance.org/2012/09/whats-my-it-strategy.html
- 8. 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’
- 11. Enterprise doesn’t choose stuff People do Some of those people work for Enterprise
- 12. Users
- 13. Who are the users?
- 14. Don’t let things get too complex (and try not to let Conway’s law take hold)
- 15. User profiles 13
- 16. Users vs things you care about 14
- 19. What – Application Distribution 17
- 20. Etc. 18
- 21. Containers
- 22. Frameworks Container Frameworks and Containers - Overview 20 NativeWeb Hybrid (HTML5)
- 23. Why have a container? Stuff you care about (=== local state) Container Everything else Everything else Everything else Everything else Everything else
- 24. Containers enforce policy Stuff you care about Container • Authentication • Encryption • Key management • Network connectivity • Jailbreak detection • Remote wipe • Etc.
- 25. Mobile device management (MDM) • The device is the container • This is how things have worked in the Enterprise PC world for many years. So many people are comfortable with the model. Container
- 26. Mobile application management (MAM) • The application is the container • This is relatively new, and hence a little scary. Container
- 27. MDM and MAM aren’t mutually exclusive Container Container
- 28. MAM can be multi tenant Container Container ContainerContainer
- 31. MAM vs MDM 29
- 32. Frameworks
- 33. Frameworks Container Frameworks and Containers – Overview (Redux) 31 NativeWeb Hybrid (HTML5)
- 34. Framework characteristics Web Hybrid Native Cross platform Yes Yes No Local state (offline capable) Limited Yes Yes Access camera, GPS & accelerometers No Yes Yes Dev tools HTML5/CSS/JS Mostly HTML5/CSS/JS [1] Various (Java, Objective C, etc.) 'Shiny'[2] Good Better Best Performance OK OK Optimal 32 [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
- 35. Can HTML5 ever be enough? The YES camp The NO camp
- 36. Can HTML5 ever be enough? The don’t seem to care camp
- 37. This is not a hybrid strategy xkcd.com/1174/
- 38. There is another way
- 39. Commercial MAM In house container Frameworks and Containers – full Picture 37 NativeWeb Hybrid (HTML5) 3rd party apps Mobile SDK Web SDK Thin client enabled legacy apps
- 40. Desktop
- 41. 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.
- 42. A Chromebook diversion • HMTL5 mostly • NaCl takes up the slack – SSH – RDP – Games? • Seems like a toy?
- 43. Chromium to the rescue
- 44. Wrap up
- 45. Users’ why drives the who, what, how and when 43
- 46. Use a container to enforce policy Stuff you care about (=== local state) Container Everything else Everything else Everything else Everything else Everything else
- 47. Choose frameworks to suit use cases 45 NativeWeb Hybrid (HTML5)
- 48. The jury is still out 46
- 49. Thanks for listening Are there any questions?
- 51. Watch the video with slide synchronization on InfoQ.com! http://www.infoq.com/presentations/UX- mobile-consumerization