Determining What Makes a Good API
From APIDesign
(Difference between revisions)
(→Have You Ever Wondered...?) |
(→Have You Ever Wondered...?) |
||
| Line 2: | Line 2: | ||
Have you ever searched for the root reason why some of APIs you liked more than others? Are those APIs that you liked the most also those most easily usable? I was thinking about this a lot. First of all I broaden the meaning of the term API and let | Have you ever searched for the root reason why some of APIs you liked more than others? Are those APIs that you liked the most also those most easily usable? I was thinking about this a lot. First of all I broaden the meaning of the term API and let | ||
| - | [[Determining What Makes a Good API|the chapter 3]] define what it means an API, | + | [[Determining What Makes a Good API|the chapter 3]] define what it means an API, explain why and enumerate various [[APITypes]]. Then I also look at the basic objective criteria to ensure an API is really good. |
Revision as of 20:59, 13 August 2008
Have You Ever Wondered...?
Have you ever searched for the root reason why some of APIs you liked more than others? Are those APIs that you liked the most also those most easily usable? I was thinking about this a lot. First of all I broaden the meaning of the term API and let the chapter 3 define what it means an API, explain why and enumerate various APITypes. Then I also look at the basic objective criteria to ensure an API is really good.
Follow
