it depends. For most, very important, but for my previous project it didn't really make sense-- there wasn't really anything to make an API for. So I went with "somewhat important".
Swagger UI allows development team to visualize and interact with the API’s resources without having any of the implementation logic in place. Learn more.
well, then human-computer interfaces are also 'API's. I don't think they are though. APIs imply specificity and rigidity (doesn't contradict with parametricity). So, an API doesn't exist explicitly for programs that do just one thing.
Programs like ed / sed / find, however, create an API within UNIX runtime by making rigid decisions about how to run completely different code paths depending on the arguments supplied.
I work since 30 years in software development area and everything needs an API. Btw., we distinguish between private, protected and public API and I guess you mean the public one.
A public API is very important if you pass control over input, output or configuration to the consumers. It takes effort to maintain it (because it's a second interface beside your main frontend), but it's a worthwhile investment in customer loyalty.
I have used a lot of software in my life. I estimate that I have used an API to access less than 10% of it. It was certainly important for that 10%, but to build APIs into the other 90% would be a huge misallocation of resources.
For instance I don't need an API for my calculator app. I have many other ways to programmatically skin that cat.
At least when I’m doing software evals at work it’s a hard requirement. And generally not just an api but an api that the main front-end consumes exclusively. Otherwise you end up with apis missing critical features.
if I’m trying to automate something repetitive and I have to resort to xdotool or keyboard maestro that’s a good way to get on my “looking for alternatives” list.
James M.
•RetroChip :sgicube:
•REST API Documentation Tool | Swagger UI
swagger.ioPhil L.
•Jons Mostovojs
•Evan Prodromou
•Jons Mostovojs
•Evan Prodromou
•Jons Mostovojs
•Programs like ed / sed / find, however, create an API within UNIX runtime by making rigid decisions about how to run completely different code paths depending on the arguments supplied.
Aljoscha Rittner (beandev)
•A public API is very important if you pass control over input, output or configuration to the consumers. It takes effort to maintain it (because it's a second interface beside your main frontend), but it's a worthwhile investment in customer loyalty.
So yes, very important. 👍
John Socks
•For instance I don't need an API for my calculator app. I have many other ways to programmatically skin that cat.
Mike Garuccio
•Evan Prodromou
•I think it's very important. I don't like to use products over a certain size that aren't hackable by me or others.
:heart_pan: jo
•Ronathon Livingston Seagull
•