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
- Someone Please Build My Open, Interactive, Portable, And Visual API Documentation Toolkit
- Dwolla Using Slate For An Evolved API Documentation Experience
- Crazy Mess Of URLs Across 400 Of The APIs In My Stack
- Reworking My API 101 Content: Consuming APIs
- I Need Help To Make Sure The Dept. of Agriculture Leads With APIs In Their Parks and Recreation RFP
- What Is The Biggest Challenge For Fraud Detection API SiftScience?
- Reworking My API 101 Content: Providing APIs
- What I Spent Ada Lovelace Day Working On
- An Outside-In Approach To Jumpstarting An API Effort At The University of Oklahoma
- Exposing Dictionaries From My API Collections