|
|
|
|
|
by giobox
1122 days ago
|
|
Debatable - supporting a small number of users on the public API may be a legitimate technical debt issue, and a running cost as the API can't change without a lot of documentation, release planning to support all those third party stakeholders etc. Your future internal work has to remain compatible with legacy design choices if you don't want to shutdown/change the existing public end points - the list of issues has potential to be pretty big. Public APIs by their nature can't introduce major change too often without upsetting existing communities. If the API is solely for your own consumption, this can be simpler, and of course third party clients are harder to monetize as the kinds of ads you can serve are going to be restricted to what you can force a third party client to receive and render. If the number of users on third party clients is really low, all of the above can carry more weight in internal business case style discussions too. |
|