4 ms·
Nicely wrapped-up public APIs with a pleasant presentation & small learning curve require tradeoffs. Why force your own app & website to pay those costs?
by bananaface 6y ago
Nicely wrapped-up public APIs with a pleasant presentation & small learning curve require tradeoffs. Why force your own app & website to pay those costs?
- JamesSwift 6y agoYou dont "force your site to pay these costs", you design your clients as consumers from day one and get consumable external APIs for free.
- bananaface 6y agoHiding the costs, minimising the costs or "integrating them well with your platform" do not erase the costs.
- mattwad 6y agoDo most companies need an external API?
- therealdrag0 6y ago3/4 places I've worked have an external API. It might not be "public" but often enterprise customers want to pull their data for their own mangling.
- haggy 6y agoThis is a common "holy grail" that I've never seen any company pull off successfully. Like others have said you rarely have the ability to build a simple-yet-powerful API that perfectly services both your company proprietary apps and 3rd party clients. The requirements are almost always at odds with each other.
- Pokepokalypse 6y agoIt certainly takes a huge amount of discipline, which is wholly absent in most service companies.