Get Some REST
The why and how of great APIs
Allen Pike, Steamclock Software
APIs in 2013
Great APIs are table
stakes
• UI is for users
• API is for developers
• They need to be clear, fast and
easy
Mobile Platforms
APIs are spreading
APIs are restricting
Different models,
different APIs
different APIs
• Up front purchase
• Pure adoption
• A subscription SaaS
• API is the pro...
Help us help you
• Internal developers
• Consultants
• Partners
• Customers
• Fans
Building a great API
APIaaS
No surprises please
• Consistent
• Standard
• Plain
• Boring
#!QOX!#
on,361926297#!QOX!#Daniel Burka,Google Ventu
o-founder,@apike,917292#!QOX!#Tobias Lütke,S
ae,29817237#!QOX!#Robert...
Enter REST
• REpresentational State Transfer
• The modern best practice
• Uniform methods, no surprises
• Contrasts with S...
RESTing up
• GET,POST,PUT,PATCH,DELETE
• Embraces HTTP
• Explorable with simple tools
• Fundamentally scalable
JSON
{ "XML": [ "Verbose",
"Heavy Handed",
"Overkill" ], "JSON": [
"Human Readable",
"Lightweight", "The new gold
standard...
The magic formula
JSON
gzip
https
Care and feeding
Future proof your
API
• Always version
• Sometimes you release a bad
API
• New versions mark breaking
changes
• Deprecate ...
Support your API
• Documentation is just the seed
• Blog for news
• Forums and Stack Overflow for
help
• Intercom.io for a...
Drive adoption
• Promote novel API uses
• Fund hackathons and
sponsorships
• SEO
• Double down on examples and
docs
• Roya...
Recap• APIs are crucial
• Follow standard REST design
• Return JSON, gzipped, over
https
• Support with great
documentatio...
Go make great
things.
apike
steamclock.com
Get the slides here!
Get Some REST: Building Great APIs for Great Apps | Allen Pike, Steamclock Software
Get Some REST: Building Great APIs for Great Apps | Allen Pike, Steamclock Software
Get Some REST: Building Great APIs for Great Apps | Allen Pike, Steamclock Software
Get Some REST: Building Great APIs for Great Apps | Allen Pike, Steamclock Software
Get Some REST: Building Great APIs for Great Apps | Allen Pike, Steamclock Software
Get Some REST: Building Great APIs for Great Apps | Allen Pike, Steamclock Software
Get Some REST: Building Great APIs for Great Apps | Allen Pike, Steamclock Software
Get Some REST: Building Great APIs for Great Apps | Allen Pike, Steamclock Software
Upcoming SlideShare
Loading in …5
×

Get Some REST: Building Great APIs for Great Apps | Allen Pike, Steamclock Software

394
-1

Published on

Allen Pike, Co-Founder, Steamclock Software

With the modern explosion of apps and platforms, building APIs has become a core skill for any technology business. Building great web based REST APIs will make scaling your business easier, allow third parties to accelerate your growth, and make supporting new platforms and devices much easier. We'll see why and how building great APIs is key to building great software.

Attendees will learn:
- The state of APIs in 2013
- What makes for a great API
- How to make developers love you
- How to feed and care for your APIs

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
394
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • - I run Steamclock Software- At Steamclock, we build iOS, Android, and JavaScript apps - Our work has been featured by Apple, CNN, and Fast Company- Before founding Steamclock, I was a Software Engineer at Apple
  • Triopoly No explosion of viable platformsNo one platform dominatesJavaScript apps increasingly consume APIs
  • Sep 2012: Twitter restricts their APIMar 2013: Netflix restricts their APIJul 2013: Google cans ReaderWhat is going on?
  • Twilio, Urban Airship, Stripe Github, dropbox Instapaper
  • Great APIs lead to great apps
  • Apple iCloud APIsDropbox APIParse (now owned by FB)Other APIs as a Service
  • It was like an archeological dig The CTO had no idea this was happening
  • Not a silver bullet, but at least bronze
  • Some Enterprises will demand XML or other noise, but provide JSON by default
  • it's cheap, it's secure, it's easy to support now saves time and bandwidth. Stack Overflow doesn't even accept GZIP off, this is becoming more common
  • Story This is an alpha-stage platform built by a team of 3. The docs were so thoughtful that Justin trusted them immediately Docs are a marketing message
  • Swagger is a tool and specification for generating API docs
  • This is on the homepage of stripe.com. Hell yes. Show both a simple and a complex example
  • Documentation needs to be googled Reasonable SEO No PDFs, no login walls
  • Twilio is the top 3 results The #1 result is their REST API docs!
  • Versions telegraph and enable change Sets the expectation that things may change
  • Start by solving a problem
  • APIs all the way down The Amazon SOA architecture
  • Get Some REST: Building Great APIs for Great Apps | Allen Pike, Steamclock Software

    1. 1. Get Some REST The why and how of great APIs Allen Pike, Steamclock Software
    2. 2. APIs in 2013
    3. 3. Great APIs are table stakes • UI is for users • API is for developers • They need to be clear, fast and easy
    4. 4. Mobile Platforms
    5. 5. APIs are spreading
    6. 6. APIs are restricting
    7. 7. Different models, different APIs different APIs • Up front purchase • Pure adoption • A subscription SaaS • API is the product
    8. 8. Help us help you • Internal developers • Consultants • Partners • Customers • Fans
    9. 9. Building a great API
    10. 10. APIaaS
    11. 11. No surprises please • Consistent • Standard • Plain • Boring
    12. 12. #!QOX!# on,361926297#!QOX!#Daniel Burka,Google Ventu o-founder,@apike,917292#!QOX!#Tobias Lütke,S ae,29817237#!QOX!#Robert Scoble,Rackspace,St utsol,500px,CEO,@oleggutsol,103872#!QOX!#Ell ngh,Tempo AI,CEO
    13. 13. Enter REST • REpresentational State Transfer • The modern best practice • Uniform methods, no surprises • Contrasts with SOAP RPC vinaysahni.com/best-practices-for-a-pragmatic- restful-api
    14. 14. RESTing up • GET,POST,PUT,PATCH,DELETE • Embraces HTTP • Explorable with simple tools • Fundamentally scalable
    15. 15. JSON { "XML": [ "Verbose", "Heavy Handed", "Overkill" ], "JSON": [ "Human Readable", "Lightweight", "The new gold standard" ]}
    16. 16. The magic formula JSON gzip https
    17. 17. Care and feeding
    18. 18. Future proof your API • Always version • Sometimes you release a bad API • New versions mark breaking changes • Deprecate and document
    19. 19. Support your API • Documentation is just the seed • Blog for news • Forums and Stack Overflow for help • Intercom.io for actual support
    20. 20. Drive adoption • Promote novel API uses • Fund hackathons and sponsorships • SEO • Double down on examples and docs • Royal decree
    21. 21. Recap• APIs are crucial • Follow standard REST design • Return JSON, gzipped, over https • Support with great documentation • Scale with versioning and marketing
    22. 22. Go make great things. apike steamclock.com Get the slides here!

    ×