Don’t build a general purpose API to power your own front end (2021)
It might be that for the author specific case (which we dont know in details) maybe this is a good approach.<p>In general I disagree with almost any idea that tries to fix some problems by adding coupling between components. I think the main thesis is where there is a false assumption:<p>&gt; Your frontend can finally focus on presentation and UI. Your backend can finally focus on implementing exactly what’s needed.<p>If you make backend create one API call for each page, you will NOT get FE focusing on UI and backend on something else. You will get FE focusing on UI and BE focusing on UI and something else.<p>I do get the feeling of rebellion against common wisdom that is FE and BE as separate components.<p>When I was junior programmer (not suggesting here that author is junior, just talking about my experience) I often found myself rebelling against common programming wisdom.<p>Now, after more than a decade of seeing so many changes and request I think those old programmers that gave us that old wisdom about separating concerns and losse coupling are right.<p>I could boil down probably all old advice into the following 3 small pieces:<p>1. Write code. Not too much. Mostly simple, short and loosely coupled. 
2. Go against common wisdom when you understand the tradeoffs. When not sure, pick the common wisdom.
3. You can maybe fix technical issues with more people, but can never fix organizational issues with code.