"APIs as a growth tool of your startup" par Nicolas Grenié

•

3 likes•816 views

Par Nicolas Grenié de 3scale. Inscrivez-vous au prochain meetup! http://www.meetup.com/StartupWorkshop Inscrivez-vous à la newsletter pour ne pas rater les prochains évènements ! http://www.thefamily.co/events/ On adorerait votre feedback & suggestion ! https://thefamily.typeform.com/to/KlGLnM?date=16/04/2015

API as a growth tool
API Workshop at TheFamily
Paris, April 16, 2015
Nicolas Grenié @picsoung
Hacker in Residence at 3scale.net
Out-of-the-box API Management
@3scale

The Family - April 2015 Nicolas Grenié - picsoung
Agenda
• 1. What is an API
• 2. Why you should use APIs
• 3. Why you should have an API

Using an API saves you
human resources
time
money

EXtra Revenues
source: http://www.slideshare.net/apigee/the-walgreens-story-putting-an-api-around-their-stores

EXtra Revenues
✴QuickPrint API, 13x partner growth
source: http://www.slideshare.net/apigee/the-walgreens-story-putting-an-api-around-their-stores

EXtra Revenues
✴QuickPrint API, 13x partner growth
✴Revenue share with developers
source: http://www.slideshare.net/apigee/the-walgreens-story-putting-an-api-around-their-stores

EXtra Revenues
✴QuickPrint API, 13x partner growth
✴Revenue share with developers
✴Apps using SDK on top charts
source: http://www.slideshare.net/apigee/the-walgreens-story-putting-an-api-around-their-stores

EXtra Revenues
✴QuickPrint API, 13x partner growth
✴Revenue share with developers
✴Apps using SDK on top charts
✴Increase in foot trafﬁc in stores
source: http://www.slideshare.net/apigee/the-walgreens-story-putting-an-api-around-their-stores

Innovation
Source: http://www.slideshare.net/faberNovel/why-shouldicareaboutap-is4/53

Innovation
✴Only 1 app developed by Fitbit in-house
Source: http://www.slideshare.net/faberNovel/why-shouldicareaboutap-is4/53

Innovation
✴Only 1 app developed by Fitbit in-house
✴Third party apps in Fitbit’s ecosystem accumulated are
worth $1m of development cost
Source: http://www.slideshare.net/faberNovel/why-shouldicareaboutap-is4/53

Innovation
✴Only 1 app developed by Fitbit in-house
✴Third party apps in Fitbit’s ecosystem accumulated are
worth $1m of development cost
✴Powerful to be on many platforms easily
Source: http://www.slideshare.net/faberNovel/why-shouldicareaboutap-is4/53

Efficiency
Source: http://apievangelist.com/2012/01/12/the-secret-to-amazons-success-internal-apis/

Efficiency
✴Wrap every internal service with an API – or you are ﬁred
Source: http://apievangelist.com/2012/01/12/the-secret-to-amazons-success-internal-apis/

Efficiency
✴Wrap every internal service with an API – or you are ﬁred
✴Better re-usability, quicker integration, spot opportunities, get to market quicker (AWS)
Source: http://apievangelist.com/2012/01/12/the-secret-to-amazons-success-internal-apis/

mobile
customer eco-system
partner eco-system
content distribution
API as a Business
An API DIFFERENT
GOAL

API Management
✴Tools to manage API program

API Management
✴Tools to manage API program
✴Access-Control / Security

API Management
✴Tools to manage API program
✴Access-Control / Security
✴Analytics

API Management
✴Tools to manage API program
✴Access-Control / Security
✴Analytics
✴Monetization

API Management
✴Tools to manage API program
✴Access-Control / Security
✴Analytics
✴Monetization
✴Developer Experience (DX)

*inspired by Kevin Lacker https://www.youtube.com/watch?v=qCdpTji8nxo
intuitive documented opinated
keys of a successful API

Take-away
Exposing API is not enough. Make sure you
secure, monitor and manage APIS
Consider API-ﬁrst design
Use APIs when you can
Your API needs to be aligned with
business strategy

Nicolas Grenié
Hacker in Residence at 3scale.net
Out-of-the-box API Management
@3scale
API as a growth tool
API Workshop at TheFamily
Paris, April 16, 2015

This document provides an overview of how to rapidly prototype an app. It discusses ideating app ideas, designing prototypes with sketches, developing click-through demos using HTML and JavaScript, and deploying to mobile devices using tools like TestFlight and Zubhium. The presentation establishes guiding principles like "budget = lifestyle" and "document everything", and recommends generating many app ideas and using visual comps to get buy-in. It also includes a shopping list of recommended tools and platforms for prototyping like UI Stencils, GitHub, and Apigee services.

API as a Growth Tool

3scale

Road to Black Friday 2015: How L.L.Bean Prepares for Traffic Spikes

Apigee | Google Cloud

Your Black Friday or Cyber Monday success can depend on being ready long before the holidays. Kris Kleva, eCommerce Technical Lead at L.L Bean, joins us to share the retailer’s journey, including the growth of its API program, and how the company does performance testing for high traffic events like Black Friday. View the webcast on youtube: https://youtu.be/Mb_kZ1qojlI Listen to the podcast version here: http://bit.ly/1IgEv3q

End to End Testing: Bug Squashing for API Developers

Apigee | Google Cloud

Presentation from the developer track at I Love APIs London 2016 featuring Ozan Seymen, Apigee and Sean Davis, Apigee. This presentation focuses on API testing best practices using open source tools and frameworks. Ozan Seyman and Sean Davis of Apigee will cover API testing methodologies including behaviour driven development and test driven development. Join to learn API testing best practices for Apigee development, how to apply popular testing methodologies in API development lifecycle, and to see live demonstrations of popular open source testing tools (cucumber, gherkin, apickli and others).

Deep-Dive: How Can APIs Help You Innovate? (Partner Ecosystems)

Apigee | Google Cloud

The document discusses how APIs can help organizations innovate by building ecosystems. It outlines how early integration approaches required point-to-point connections but APIs now allow maximum reuse and open the door to more partners. The document presents examples of how Phillips Hue, Swisscom, and The World Bank used Apigee Edge to build successful digital ecosystems and external developer programs through their API strategies. It emphasizes that ecosystems require frictionless experiences for developers and visibility into the digital value chain.

I Love APIs 2015: Create Design-driven APIs with Node.js and Swagger

Apigee | Google Cloud

This document discusses API documentation and the use of Swagger to define APIs. It notes that API documentation is critical for others to understand what an API does. Good documentation includes examples and tutorials in addition to reference documentation. The document then introduces Swagger as a way to define APIs in JSON or YAML, describing available operations, inputs, outputs, authentication, and more. It discusses using Swagger both by generating code from Swagger definitions or by driving the code implementation from the Swagger specification. The document argues that starting with Swagger specifications can avoid duplication and better support code generation and documentation. It provides an example of defining a Node.js API using the Swagger tooling.

Postman Webinar: "API Governance with Postman"

Postman

State of the API: Insights Into the Future of APIs

Postman

The document discusses the state of APIs based on a survey of over 13,500 API professionals. It finds that while developers make up over half of API professionals, non-developers are also significant users. The top obstacles to producing and consuming APIs are lack of time for production and lack of documentation for consumption. The future of APIs is predicted to include continued investment and focus on microservices and serverless architectures.

Keynote at APIDays Melbourne 2016, Steven Willmott - 3scale. Organizations have recognized that making available IT systems as APIs for both internal and external developers can create huge new opportunities for agility, products and ultimately revenue. However, while this "platform thinking" holds great potential, it can be extremely challenging to determine how to deliver on these opportunities. In this talk we'll look at how focusing on the value APIs can deliver helps underpin genuine success for an API program and an organization's platform initiatives as a whole.

YAGNI, YMMV and APIs: building a hybrid strategy for your API platform.

Diogo Lucas

This document discusses strategies for building an API platform and discusses factors to consider like teams and the Dunbar number. It analyzes different strategies like single-team APIs that are optimized for a single team but have low reuse, ecosystem APIs that are optimized for adoption but have high overhead, and near-team APIs that reflect your organization. It also discusses structures for your organization like the centralized glacier which is stable but hard to experiment with, shipping your org which is easy for producers but hard for consumers, and keeping APIs internal which is easy for producers but unstable for consumers. The best strategy balances ease for consumers and producers while allowing for autonomy and central governance.

Enterprise ecommerce-webinar 1

Postman

A Checklist for Every API Call

Apigee | Google Cloud

Checklists encourage efficiency, consistency, and safety. But how does that apply to APIs and API programs? How do checklists help organizations succeed with APIs, and do so with various roles across business, IT, operations, and security? This webcast discussed how to build a simple, repeatable approach to build a successful API program—one that moves the needle—by avoiding the common pitfalls of complex, multi-team projects. If you’re an architect, CISO, ops engineer, or API business or product owner, this is for you.

Why You Need a Developer Relations Team for Your API

Postman

Developer Relations teams focus on three key areas: 1) improving the developer experience through SDKs, documentation, demo apps and support, 2) building a developer community through events, conferences and an online community, and 3) collecting feedback across multiple channels to understand developers and improve the API. Having a DevRel team leads to a happier developer community, easier onboarding, more successful customers, and making the API a leader in its market.

Postman for Enterprises

Postman

This document provides an overview of Postman's enterprise capabilities from Sanjeev Sisodiya, VP of Customer Success at Postman. It discusses how Postman can accelerate key business processes by providing a developer experience platform, ensuring API quality, security and governance. It highlights some of Postman's enterprise customers and describes how the combined capabilities around developer productivity, quality, security and governance form Postman's API platform. The document encourages attendees to reach out if their organization could benefit from an enterprise API platform.

Appium - Reality check on the world’s leading Open Source Framework for Mobil...

Asaf Saar

Appium is clearly the world leading framework for mobile apps test automation. Adoption of Appium is in constant rise, and for the good reasons. Yet, in many cases those who do their initial steps or even progressing with the framework realize that the world is not that simple, challenges arise, limitations are discovered and one can find himself wondering whether the right decision was taken in investing the time and money into it (yes... open source cost you money). In this talk we will pause for a while, review why Appium is an outstanding framework, while also do a reality check of the cons and pros of Appium, helping you make the best out of it, or at least have a clear understanding of what's ahead of you.

Light Up Your Intranet with 10 Cools Apps

Ayman El-Hattab

The document announces an online conference on June 17th and 18th 2015 about lighting up intranets with 10 cool apps and add-ins. It provides details on speakers and their backgrounds and objectives. It outlines and demonstrates apps including AvePoint Meetings, Yammer app for SharePoint, Yammer Embed, Mavention Birthdays, Mavention Anniversaries, Mavention Profile Completeness, myFAQ, Quick Poll, and Nintex Workflow and Forms. Attendees are asked to provide feedback on the session.

Enterprise E-commerce Webinar Series, Episode 2: Deploying and Monitoring You...

Kin Lane

Note: This webinar is the second in Postman's three-part webinar series on implementing an API-first strategy in enterprise e-commerce. The series, hosted by Postman Chief Evangelist Kin Lane, will walk you through key topics and how-to content via a hypothetical e-commerce enterprise, Union Fashion (see it on GitHub). Continuing with our series, the second webinar will dive into actually deploying and monitoring an API using the Postman platform. We will take the API we developed as part of our previous API-first webinar, and actually bring it to life by focusing on the following areas: - Versions - Monitors - Mocks - Environment - Documentation - Feedback Loops The full video for this session can be found at: https://www.youtube.com/watch?v=jO2M_kqb-jo&t=1659s

Demo: New open banking platform

Apigee | Google Cloud

API Lifecycle Management

Postman

API lifecycle management enables setting guidelines for how contributors, stakeholders, and consumers interact with an API throughout its different stages. It focuses on how teams collaborate across the planning, design, development, testing, deployment, and versioning/deprecation of an API. API lifecycle management ensures all parts of the process work together to build an API that meets its goals. The presenter demonstrated API lifecycle management using Postman.

Common Security API Issues and How to Mitigate Them Using Postman

Postman

Postman Public Workspaces: The First Massively Multiplayer API Experience | W...

Postman

Why APIs Call for 2xs the DevOps

Postman

The document discusses APIs and DevOps practices. It begins by covering best practices for APIOps and how shifting to a microservices architecture can help teams develop and deploy applications faster. It then discusses how DevOps practices like continuous integration, delivery, infrastructure as code, and monitoring can benefit API development cycles by improving speed, security, collaboration, reliability and more. The document provides examples of how Amazon has shifted from monolithic to microservices approaches and emphasizes treating infrastructure like code and establishing automated pipelines with monitoring from the start.

LaunchKit

cocominap

Inside mind of a successful platform architect / Gartner APPS 2016

3scale

The document discusses three principles for platform success: focus on true value, enable rather than own platforms, and ask for budget contributions ("tithes") that are distributed among beneficiaries. It argues platforms should solve real business problems, empower external development rather than internal ownership, and fund themselves through a share of facilitated business value rather than isolated grants. Examples from Maps Credit Union, KeyBank, Schiphol Airport, 3Scale, SimilarWeb and Fitbit are given to illustrate successful application of these principles. The document concludes by emphasizing measuring business value over technical metrics.

Two Ton API Client

Brian Mulloy

Twitter users are generating 110 million tweets per day. Between 8pm & 10pm local time in the US, 20% of all Internet traffic is driven by one company: Netflix. Interestingly, most of the traffic for Netflix and Twitter does not come from the Web browser. Twitter has more than 300,000 registered applications running on devices of all shapes and sizes. Netflix streams content to the iPhone, Nintendo Wii, Playstation, iPad and many others. All of this innovation is driven by devices - often mobile devices - accessing web APIs. Web APIs, Application Programming Interfaces, allow computers to talk directly with one another. It's how the Nintendo Wii talks to the Netflix server. It's how an iPhone App, like TweetDeck, talks to the Twitter server. As we enter the golden age of web APIs, we have to ask: what does all this mean for one of our biggest mobile devices, the car? In this ignite session, we'll explore what is possible when we imagine the automobile as a two ton web API client.

apidays LIVE Paris - Data with a mission: a COVID-19 API case study by Matt M...

apidays

Applying Design Priciples to APIs - 1 of 4

Brian Mulloy

This document discusses applying design principles to APIs. It is divided into four parts. Part I focuses on empathizing with developers by following best practices throughout the development cycle, handling errors transparently, and keeping the API status and methods clearly visible. The document provides checkslists of specific things API providers can do at each stage to be helpful, harmless, and honest from the developer perspective. Parts II through IV will cover additional design principles for APIs.

APIs for your Business + Stages of the API Lifecycle

3scale

The document discusses APIs and the API lifecycle. It describes four stages of the API lifecycle: plan/design, build/integrate, operate/manage, and share/engage. Each stage is important to consider when developing APIs. The document also provides examples of how companies have benefited from APIs by creating new revenue sources, increasing reach, fostering innovation, and improving efficiency. It emphasizes the importance of managing APIs after they are built to secure access and monitor usage and traffic.

"How to create an efficient API.. with a business model?" by Nicolas Grenié

"APIs as a growth tool of your startup" par Nicolas Grenié

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to "APIs as a growth tool of your startup" par Nicolas Grenié

Similar to "APIs as a growth tool of your startup" par Nicolas Grenié (20)

More from TheFamily

More from TheFamily (20)

"APIs as a growth tool of your startup" par Nicolas Grenié