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.
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)
29. @bmkatz
• MADP are designed to accelerate mobile application
development
• Write Once - Deploy Everywhere
• Familiar languages (.net, C#, etc)
• Codeless (the new it thing)
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
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)
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)