Posted on 08-25-2014
I was looking around the Google Developer area as part of some regular work, and I noticed an interesting page Google has under their mapping session, that help users decide which API they need based upon their goals.
As the page says: "The API picker lists the most common things you may want to do on a map or with location-based data, and suggests the API that most suits your needs. For details about each API, follow the links to the related documentation."
I don't think that the table layout Google uses is a particularly good one, resulting in a pretty busy looking matrix. I don't think it is a perfect solution, but I like the idea of providing developers with some sort of assistance in understand which API to use, based upon their goals.
This is something that a larger API provider would probably do, but a simple little needs calculator that could help users translate what they are looking for into what the API does, is an interesting concept to play with for some API providers.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Maybe I Am Missing Something, But Where Is Your Pricing Page?
- I Find It Interesting That Wordnik Created The API Definition Format Swagger
- Autogenerate Runscope-powered API SDKs Using APIMatic
- Where Do We Start With APIs At The University of Oklahoma?
- What I Would Look For When Hiring a Modern API Developer?
- The U.S. International Trade Commission Includes APIs In Latest Report
- Thank You @3Scale For Investing In The Community With @APIStrat
- Introducing API.Report, A Community API News Site
- Extract Knowledge From Audio And Video Using The Clarify API
- My API 101 Workshop At @APIStrat In Chicago Next Week