> If you know you will need to provide a good public API, building it from the get go and a React/Angular app on top might still be worth it. That is a differe

> If you know you will need to provide a good public API, building it from the get go and a React/Angular app on top might still be worth it. That is a different point than you made earlier in your comment though. That you start building an API on the server side does not mean you’re creating a good, well-balanced, API suitable for public consumption (being consumption in other teams or even other companies).