2 ms·
This was a very apropos read for me, since I'm working on my next app by starting with the API. I have been working with quite a few API's and I've found that
by byoung2 16y ago
This was a very apropos read for me, since I'm working on my next app by starting with the API. I have been working with quite a few API's and I've found that a lot of them felt like their creators never used them. So I'm building an API that I would use myself, and I'm forcing myself to live up to that promise by building the rest of the app on top of the API. I'll let you guys know how that goes!
- hsmyers 16y agoThe best way to create an API that feels like their creators never used them is to build one that you would use yourself. If you want to build one that others can use and use easily then you need to put yourself in their shoes, not your own. Otherwise it's just one more library built on some one else's idea of a good time. That said if absolutely no one else is ever going to see, let alone use this API, then certainly build what works for you... just remember the maxim of writing as though the person/maintainer after you is a psychopath who knows where you live.
- jamii 16y agoOr even better, write the app's frontend using the public API (and only the public API, no cheating).