Mobile-Enabling APIs for Developer Ecosystems

by Richard Mendis @ APIStrat 2014 in Chicago

Transcript

1. © Copyright 2013 AnyPresence, Inc. All rights reserved. Supporting the Evolving Needs of Developer Ecosystems Richard Mendis Chief Product Officer, AnyPresence 1
2. Internet of Things (All Smart Devices, Cars, Appliances, Wearables, etc.) # of Devices Evolving Connected Technology Landscape 2 Time PCs Post-PC (Smartphones, Tablets, TVs, etc.) Images: Brad Frost The most successful organizations will be those who enable strong developer ecosystems
3. Forecast: “Resurgence” of Native Apps, More Fragmentation 3 Relative Computing Power Amount of Devices “Long-tail” IoT devices with embedded computing capabilities Mainstream personal and business computing devices Browser-supported apps possible Primarily native app driven
4. Development Expectation Challenges 4 Development cycles down to 6-8 months or less, from 12-18 Development budgets not increasing to match mobile needs Complexity across Front-end, back- end and secure, scalable integration Development, Design, Develop, Test all work on the same cadence: Rapid Prototyping and Ongoing Updates LESS TIME LESS BUDGET MORE COMPLEX Source: Forrester Research MORE DYNAMIC
5. API Mobile Adoption Challenges and Opportunity Documentation Method § Documentation on API methods Challenge § Limited ability to understand context of methods § Docs can get out of date Result ✘ Poor adoption ✘ Takes longer to build apps 5 Live Apps, Dynamic Sample Code § Live, interactive sample app § Fully working app with source code and SDK § Maintaining code base across multiple platforms § Providing server-side deployment options for complex scenarios ✔ Significantly improve developer adoption ✔ Faster time to market with customized sample app and portable source code Mobile Adoption Static Sample App Code § Provide a link to some example app in one platform § More difficult to maintain (requires multiple skillsets) § Not customized to a specific use case § Limited data sets ✘ Expensive to build and maintain ✘ Addresses limited use cases Static Sample Code Snippets § Snippets of code in a few languages § API Explorer § Difficult to maintain § Not customized to a specific use case ✘ Doesn’t provide a fully working example ✘ Takes longer to build apps Incremental Improvement Opportunity: Exponential Improvement
6. Beyond APIs: Improving Ecosystem Adoption 6 APIs Endpoints Only §  Takes time to interpret and implement §  Lacks app-specific mobile services; typically optimized for web apps Mobile Backend Server ü  Mobile optimized APIs, domain-specific abstraction layer ü  App-specific services and business logic Cross-platform SDKs (+docs) ü  Drop into app project ü  Familiar syntax App UI Starter Kits ü  Fully-working app ü  Editable source code Lower development hurdles, reduce time to market, and improve adoption APP DEVEOPMENT TIMEFRAME
7. SOA Example: MasterCard API to Mobile Challenge 7 Challenge: Need to enable partners to build mobile apps using MasterCard products iOS Developers HTML5/JS Developers Android Developers Developer Ecosystem: Banks and ISVs Open API Services Server component to demonstrate oAuth flow NxN Problem: This would require MasterCard developers to build and maintain individual iOS, Android, and HTML5 SDKs and sample apps, and a server. Custom apps would be impossible. iOS Sample app iOS SDK JavaScript SDK HTML5 Sample app Android SDK Android Sample app
8. SOA Example: MasterCard with AnyPresence App Launchpad 8 Solution: AnyPresence dynamically generates fully-working, customized sample apps across all mobile platforms, including a sample backend server, with optional deployment iOS SDK and App Starter Kit HTML5/JS SDK and App Starter Kit Android SDK and App Starter Kit Standalone Mobile Backend Server Developer Ecosystem: Banks and ISVs Open API Services Dynamic Generation
9. Brief Demo: Enhancing Your Developer Portal 9
10. 1 How It Works §  Define templates with pre-built integration to your product, service, or content §  Determine which features can be customized by partner or customer developers 3 PARNTERS CUSTOMERS §  Download source code for backend server, SDKs, and UI starter kits (option to compile apps and host server) §  Functional app with customizable code and deployment options Enable Developer Ecosystem Define App Templates Your Company’s Developer Portal §  Custom-branded developer portal or new functionality within existing solution §  Enables users to select a template, specify options, and generate an cross-platform apps 2 Build Developer Portal
11. Compilation and Generation in Cloud Define App Tempaltes Environment and Deployment Management Design Time API Services RUNTIME COMPONENTS (Dedicated Stack per App) Solution Overview 11 Dedicated Backend-as-a-Service (Multiple Environments Per App) Roles and Authentication Integration and Business Logic Mobile Services AnyPresence Designer Enterprise Integration and Data Storage User Interface Starter Kits Object Modeling and Business Logic Mobile Services and Extensions DESIGN-TIME PLATFORM SERVICE (Multitenant Environment) Mobile UI Starter Kits (Editable Code) Enterprise Source Systems and Data PUBLISH PUBLISH Mobile SDKs (Docs and Test Scripts) PUBLISH
12. Brief Demo: Building App Templates 12
13. Use Cases and Key Benefits Internal Use For use within the organization to build and deploy apps faster Key Benefits: ü  Efficiency / Scale ü  Enforce IT Policy 13 Partner Use For use by approved partners to enable specific functions within their apps Key Benefits: ü  Partner Enablement ü  Retain Control External Use For use by external developers, to encourage adoption of public APIs Key Benefits: ü  Adoption ü  Revenue / Brand Recognition
14. User Interface “Starter Kit” ü  Cross-platform UI code with SDK examples ü  non-proprietary, editable source code ü  Template starter kits Lessons Learned: Evolving Developer Ecosystem Needs 14 API Management ü  REST-enable HTTP endpoints ü  Usage and bandwidth throttling ü  Key management ü  Business Logic ü  Developer Portal Backend Services ü  Object Relational Mapping layer for “composite” apps ü  Cross-platform SDKs ü  Mobile-specific business logic ü  Mobile services (push, SMS, etc.) …with an architecture that accommodates the evolving needs of new devices and endpoints You need to meet the needs of mobile- enabling a developer ecosystem today… Happy Developer Ecosystem
15. Thank You! Questions? 15 Richard Mendis rmendis@anypresence.com 571-426-6000 @AnyPresence www.anypresence.com