![]() If anyone should understand how to make a web API that’s easy-to-use, it’s you. Your users are likely to be as critical of your API as you would be of theirs, and will thoroughly enjoy critiquing it.Īnd therein lies part of the irony, by the way. And whoever they are, they will have the technical sophistication (or at least will think they have the technical sophistication) to point out every little flaw in your software. You’re designing an interface for programmers, probably without even knowing who they are. You’re giving them a graphical interface and, if you’ve been doing your job right, you’ve gleaned a pretty good idea from them of what they need the interface to do.īut API development is different. ![]() Most of the time when you’re building solutions, you’re designing for end users who are not programmers, or who are generally not technically sophisticated. But how? The answer to that question is what this post is all about. In truth, it’s possible to design great web APIs that people will actually enjoy using, and that you’ll enjoy creating as well. Ever found yourself wondering “what were they thinking?” when integrating a web service via its API? If not, you’ve been far luckier than I have.Īny software developer knows how easy it is to let a project devolve into spaghetti code, and web APIs are no less prone to resulting in a tangled web.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |