The changing face of mobile apps in the future of mobile
•
1 like•623 views
The document discusses the changing landscape of mobile apps and strategies for developing them. It notes that most companies have developed fewer than 7 internal apps, and are now using existing development teams to build modern apps. It also discusses strategies like mobile app development platforms, backend as a service, and refactoring legacy apps to be more mobile-friendly. The key messages are that companies should focus on users' needs, build APIs to access enterprise data, and take a mobile-first approach to reimagining processes from the users' perspective.
Report
Share
The changing face of mobile apps in the future of mobile
- 1. The changing face of Mobile Apps in the future of Mobile
- 2. Who Am I @bmkatz • Day job: Director of Mobile Strategy @VMware • Just a nutter with a blog - http://ascrewsloose.com • Host: @themobilecast podcast • Host: #Futurebiz tweet chat (Thursdays 1PM ET)
- 3. @bmkatz
- 4. @bmkatz
- 5. @bmkatz
- 6. @bmkatz
- 7. @bmkatz
- 8. @bmkatz
- 9. @bmkatz
- 10. @bmkatz
- 11. @bmkatz
- 12. @bmkatz
- 13. @bmkatz Most companies have developed less than 7 internal apps - Gartner
- 14. @bmkatz
- 15. @bmkatz
- 16. @bmkatz
- 17. @bmkatz Companies are taking their existing application development teams and using them to develop modern apps
- 18. @bmkatz
- 19. @bmkatz
- 20. @bmkatz
- 21. @bmkatz
- 22. @bmkatz
- 23. @bmkatz Katz’s Axiom If you build a crapplication they will run!
- 24. @bmkatz • Apps you hate to use • UI • UX • Scope Creep • Not what you wanted
- 25. @bmkatz
- 26. @bmkatz
- 27. @bmkatz
- 28. @bmkatz • Adobe • Appcelerator • IBM • Microsoft (Xamarin)
- 29. @bmkatz • MADP are designed to accelerate mobile application development • Write Once - Deploy Everywhere • Familiar languages (.net, C#, etc) • Codeless (the new it thing)
- 30. @bmkatz
- 31. @bmkatz Growing Up • Templates • Fewer coding fixes per OS • More APIs
- 32. @bmkatz
- 33. @bmkatz What happens when you mix a legacy app with some virtualization, add some hocus pocus and you come out with a mobile App?
- 34. @bmkatz RMAD
- 35. @bmkatz • Alpha Software • Capriza • HopTo • PowWow • Reddo • Starmobile
- 36. @bmkatz Refactoring • Take the legacy part of an App and make it modern • Original still exists but look/feel and behavior may be different to customer
- 37. © Copyright 2015 StarMobile, Inc. All Rights Reserved AB InBev Sales Application This is the PC browser-based BEFORE view of the AB InBev Key Account Management system
- 38. © Copyright 2015 StarMobile, Inc. All Rights Reserved StarMobile Studio Visual Editor
- 39. © Copyright 2015 StarMobile, Inc. All Rights Reserved AB InBev Sales App This is the AFTER view of the AB InBev Key Account Management App that was delivered in less than five business days
- 40. @bmkatz
- 41. @bmkatz
- 42. @bmkatz • Amazon • FeedHenry/Redhat • IBM • Kinvey • Kony • Microsoft Azure
- 43. @bmkatz BaaS
- 44. @bmkatz
- 45. @bmkatz
- 46. @bmkatz App UI/UX 100% © Kinvey 2016 Delivering an App: Perception
- 47. @bmkatz UI/UX New frontend and backend features (online & offline) Security & Compliance 25% 30% 20% 10%15% Support, Scale & Manage Sub-second Enterprise Data Integration, orchestration & acceleration © Kinvey 2016 Delivering an App: Reality
- 48. @bmkatz Custom Features 25% Standard Components 75% Another way to look at it © Kinvey 2016
- 49. @bmkatz What is A BaaS • New type (?) of middleware • Decouple front end development from back end changes • Don’t produce a traditional app (build 70-85% of the app)
- 50. @bmkatz Today
- 52. @bmkatz
- 53. @bmkatz #FUN Principle Focus on the Users’ Needs
- 54. @bmkatz
- 55. @bmkatz It’s always great to have business requirements but unless you understand the use case you’ve wasted your time
- 56. @bmkatz Use case
- 57. @bmkatz
- 58. @bmkatz
- 59. @bmkatz
- 60. @bmkatz
- 61. @bmkatz
- 62. @bmkatz
- 63. @bmkatz
- 64. @bmkatz
- 65. @bmkatz An App is the interface we use to Access the Data and Manipulate it
- 66. @bmkatz Appifying the Enterprise • It’s the data stupid • Build an API to access the data • Wrap identity around it • Build apps that access the data through the API • Get Security involved in the beginning • Know what you’re building for (Biz Objective & User Needs)
- 69. @bmkatz
- 70. @bmkatz
- 71. @bmkatz
- 72. @bmkatz
- 73. * Your employees are your customers too! It’s all about the use case! How do you REIMAGINE the process to make it easier for your customers!
- 74. REINVENT
- 75. @bmkatz
- 76. @bmkatz
- 77. @bmkatz
- 78. @bmkatz
- 79. @bmkatz
- 80. @bmkatz
- 81. @bmkatz
- 82. • Still have many single use apps - but infrequent use • Single pane of glass (App) for the easy stuff • Much more productive
- 83. @bmkatz
- 84. @bmkatz
- 85. @bmkatz