10. Common API Debates
Which framework to
use?
REST/SOAP - What is
Rest anyway?
Streaming API?
Internal / External?
Versioning?
Make it public?
Should we charge?
By API Call?
Should we put rate limits
on?
Won’t it kill our Ad-
Revenue?
18. Your Value is one or more of:
1.Your Data
2.Key Functionality
3.Your Audience/Reach
That’s all people
care about
19. The Following Help but are
secondary
1. Being Cool
2. Having a Nice UI
3. Having a Nice API
None is a
reason for
people use you
per se
Lipstick / Pig
23. Different Access for Different
Targets. E.g.
An app for Seniors, who are Piano Teachers and need
a very advanced UI -> API?
A new humorous content for an 18-25 Audience
Demographic -> API?
A new advanced algorithm for predictive price plan
optimization for retailers ->API?
24. Inside Out Means…
Providing potentially deep access to your core
functionality to others at whatever level they
can handle
Reusing the core functionality of others where
you possibly can
Don’t write code
you don’t have to!
26. “A ‘startup’ is a company that is confused about –
1. What its product is. 2. Who its customers are. 3.
How to make money.”
Dave McClure, 500Startups
“A ‘startup’ is a company that is confused about –
1. What its product is. 2. Who its customers are. 3.
How to make money.”
28. Mobile Enablement
Backend for your
own Mobile Apps
Multi-platform and/
or supporting
HTML5 / SPA
Focus: stable
backend
• Often combined with others
• Assume it is not private
• Apps drive business
29. Customer Ecosystem
Data Integration for
reporting (in / out)
Increases comfort
level v’s lock in
Allows self
customization
• Normally free or bundled
• Useful for driving up-sell
• Big driver for stickiness
30. Partner Ecosystem
3rd Parties can add
value that you can’t
Can be smaller or
larger
Alternative to
manual software
integration
• Increase functionality
• Add data
• Increase reach
31. Content/eCommerce Distribution
Special case of
partners
Partners resell &
amplify
Focus: gaining
audience /
transactions
• Partners may pay
• Or be paid
• Drive transactions to core
32. API As A Business
What everyone
thinks APIs are
about…
Access / per
transaction fee
Instant gratification
• Often data on demand
• Or functionality on demand
• API is the Business
33. Internal Innovation
Sorting out internal
legacy
Cross-department
teams made more
agile
Focus: refactoring
• Increase agility
• Reduce cost
• Up developer happiness
e.g.
34. Other Models
Many companies use
multiple models
Models often change
over time
Some apply more / less
to startups
Feel free to invent new
ones
Whatever
happens: be
clear which your
model is !
59. Conclusions
Don’t get religious
Make sure you are delivering genuine value
Treat the API as your product
Focus on the early key passionate users
Decide if you are a platform or an application/service
Always enhance your core company value - do make it
a separate business