We we should be Mobile API - First, by Brad Hipps
•Download as PPTX, PDF•
0 likes•502 views
The document argues that companies should adopt a mobile API-first approach to succeed in the experience economy. It notes that the development target is no longer a single device but a connected ecosystem of devices centered around user experience. An API-first approach allows for easy discovery of existing APIs, ease of API development, comprehensive analytics on app usage and API consumption, and embraces JavaScript. This approach enables a new model of IT innovation with nimbler and more specialized systems that are loosely coupled.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (14)
Similar to We we should be Mobile API - First, by Brad Hipps
Similar to We we should be Mobile API - First, by Brad Hipps (20)
Recently uploaded
Recently uploaded (20)
We we should be Mobile API - First, by Brad Hipps
- 1. Why We Should Be Mobile API-First (Or:WinningThe Experience Economy) BRAD HIPPS, PLATFORM ON-DEMAND @appcelerator
- 2. “There is no one future state with mobile technology: As soon as one aspect stabilizes, another enters a phase of radical change. The development target is no longer a device, but a loosely-connected ecosystem of devices and services centered on a user experience.” – GARTNER ”THE FUTURE OF MOBILE APPS ANDTHEIR DEVELOPMENT”, OCT. 2014.
- 3. 0 1 MARKET PREMIUM PRICING Extract commodities Make goods Deliver services Stage experiences DIFFERENTIATED UNDIFFERENTIATED COMPETITIV E POSITION THE PROGRESSION OF ECONOMICVALUE SOURCE: Pine, B. Joseph, and James H. Gilmore. Welcome to the Experience Economy. Harvard Business Review, July 1998.
- 4. LOST BILLIONS TO… DISRUPTED BY… ANTICIPATED DISRUPTION BY… DISRUPTED BY… DISRUPTED BY… HOWTHE EXPERIENCE ECONOMY (RE)MAKES MARKETS
- 5. A revolution in experience is driving an evolution in the stack CLIENT SERVER Early 1990s One-to-one Rich UX (GUI) Distributed computing Local Network WEB Late 1990s One-to-many Weak UX (HTML-Based) Server-centric computing Global network MOBILE Today Many-to-many Rich UX (driven by mobile OSs) Distributed computing Internet of Things 1990sTOTODAY
- 6. The device explosion is here. The data isn’t.
- 7. fr THE REAL MOBILE CHALLENGE FRONT-END BACKEND
- 8. “Mobile is pushing aging web architectures to the brink.” – FORRESTER FACEMIRE, MICHAEL,TED SCHADLER, & JOHN C. MCCARTHY. ”MOBILE NEEDSA FOUR-TIER ENGAGEMENT PLATFORM:WEBARCHITECTURES CAN’T HANDLETHE NEW DEMANDS OF ENGAGEMENT.” FORRESTER RESEARCH. NOV. 2013.
- 9. Data, data everywhere AND NOT A DROPTO DRINK?
- 10. Poor data access is throttling mobile innovation 27.6% 72.4% DISAGREE AGREE Do you agree or disagree with the following statement: “Getting mobile- optimized access to data is becoming the most challenging aspect in building great app experiences, quickly.” APPCELERATOR / IDC Q3 2015 MOBILE TRENDS REPORT n = 5,778 mobile developers
- 11. Mobile API First To innovate here… Innovate here. APPSAREONLY AS GOODASTHEIR DATA
- 12. THE NEW MOBILE STACK
- 13. Traits of API-first Organizations A common, standardized tier that allows: Easy discovery of existing APIs Ease of API development; minimize bureaucracy & command- and-control Using analytics to improve the API “inventory”
- 14. v Measure what matters.* *It all matters.
- 15. Traits of API-first Organizations A common, standardized tier that allows: Easy discovery of existing APIs Ease of API development; minimize bureaucracy & command- and-control A soup-to-nuts analytics view which encompasses app usage, lifecycle metrics and API consumption
- 16. JOBTRENDS GOOGLE TRENDS Why JavaScript? THERE’S A GOOD REASON…
- 17. DYING DISTINCTIONS FRONT-END DEV (e.g. HTML, CSS, JavaScript) BACKEND DEV (e.g. PHP, Java, Python)
- 18. FRONT-END DEV (e.g. HTML, CSS, JavaScript) BACKEND DEV (e.g. PHP, Java, Python) MEETTHE NEW FULL-STACK DEVELOPER JavaScript
- 19. Traits of API-first Organizations A common, standardized tier that allows: Easy discovery of existing APIs Ease of API development; minimize bureaucracy & command- and-control A soup-to-nuts analytics view which encompasses app usage, lifecycle metrics and API consumption An embrace of JavaScript as a lingua franca
- 20. APIs enable a new IT innovation model PRESENT: “FREE-FOR-ALL” Nominal central control BYOD/A, rise of shadow IT Silos, inevitable redundancies Variable results (usability, security, performance, etc.) FUTURE: “INNOVATION EXCHANGE” Nimble and specialized, fit for purpose Looser coupling, higher cohesion Expanded ecosystem = more innovation New market opportunities
Editor's Notes
- What I particularly like about this quote is that it underlines the absolute fundamental of mobility: user experience. All the stories of mobile’s growth and its transformative powers are the result of the fact that mobile apps, done right, deliver a personalized, context-aware, simple and pleasing user experience.
- I’ve talked about how mobile is replacing the web and experience has become critically important, but I think there’s a broader shift taking place. Fifteen years ago, B. Joseph Pine and James Gilmore predicted the rise of the Experience Economy in a Harvard Business Review article. The basic premise is that business are facing a commodification of almost every kind of good or service, which will drive companies to offer exceptional experiences as it becomes the only means of differentiation We are beginning to see this play out today. Apple is arguably the best when it comes to delivering exceptional experiences and they have gone from near bankruptcy to the most valuable company on the planet. The other interesting thing to note is that winning in the experience economy does not require a company to be large. Look at Instagram, Square, Uber and WhatsApp. These are all small companies each worth billions of dollars. While these are all consumer companies, they serve as leading indicators of what’s to come for the broader market. One of the things that is making this possible is that scale itself has largely been commoditized. In fact, in many cases, size has become a competitive disadvantage, so larger companies need to figure out ways to act like smaller companies. To innovate, and to innovate quickly. So mobile is driving something much deeper than the need to create great apps. It’s changing what companies must do to be successful. The next question is what does all of this mean for IT?
- Ovum predicts the telecommunications industry will lose a combined $386 billion between 2012 and 2018reports that telecom companies count $386 billion in lost revenue to Skype, WhatsApp, others (http://fortune.com/2014/06/23/telecom-companies-count-386-billion-in-lost-revenue-to-skype-whatsapp-others/)
- Analytics provides visibility and insights into the use and adoption of mobile apps in addition to proactive problem identification that is actionable by engineering teams to shorten mean time to resolution. Our Appcelerator Platform includes both our mobile lifecycle dashboard along with our executive insights dashboard. Our mobile lifecycle dashboard targets practitioners and business users alike. It delivers visibility across the entire lifecycle and allows developers, testers and dev ops personnel to drill down into key individual areas so there is complete transparency of activities across the entire mobile app portfolio. For example, using our performance management services, apps teams can for the first time get actionable information when something goes wrong down to the file and offending line of code. As opposed to waiting for tickets in help systems to be filed and transferred over to engineering teams, now mobile app teams can in real time view the health and status of their applications as they are being used by the mobile community. Historical and real-time data Is captured to provide a direct line of sight into the working of the app by the mobile user community by those can most immediately address any problems that may occur. Our executive insights dashboard measures and historically manages key metrics around worldwide or regional adoption and engagement so business/app owners can immediately understand trends related to what target segments of mobile users are running the application and how they using the application. This provides critical insights for business owners so they can prioritize what capabilities and features should be enhanced or dropped to ensure continued use and adoption of the mobile app.
- Evolution of full-stack dev… mirrors merger of design & (front-end) developer skills/roles Same aim as this merger: better experiences, faster
- We started by looking at the new pressures on and changing nature of IT, so I owe it to you to circle back. Given how mobility is shaping the new enterprise and what Appcelerator brings to the table, what might a future state for enterprise IT look like? For starters, I don’t think the answer is simply a return to the world of old, where IT did everything. I don’t think the lines of business want that, and I don’t think you want that. We actually envision something else – call it an “innovation exchange.” In this world, IT gets to focus on doing a few things really, really well and works to empower and broker a broader ecosystem of contributors. How might this work? For one thing, having a collection of open, mobile-optimized APIs means that other participants, even external developers, could create innovations around enterprise systems and capabilities. In this model, IT becomes the enabler even of accessing new markets that the business may not have touched. (We do exactly this with our Platform and the Open Mobile Marketplace.) And one of the chief ways you monitor the effectiveness of this exchange is through analytics. Very similar to a stock exchange, you use metrics to evaluate who’s performing and who’s falling short, and you publish these to the enterprise so departments can make their own decisions about where the next app capability should come from. This may sound a little far reaching, but we don’t think it’s utopian. You can get there, and we can help.