For small team (teams are always small, since people are leaving and coming) building a medium to large sized web app (CRUD + filters, views).
Using a REST API isn't very useful from a developer productivity POV. One has to maintain a structure for request, response, query params structure.
Using GraphQL also requires that code (actually executable code). But it's better that it's executable, one can know breaks faster, and update in structures are binding to both FE and BE tasks. Both sides can still mock stuff if the other side is not done.
On that note, here's an important lesson.
For small team (teams are always small, since people are leaving and coming) building a medium to large sized web app (CRUD + filters, views).
Using a REST API isn't very useful from a developer productivity POV. One has to maintain a structure for request, response, query params structure.
Using GraphQL also requires that code (actually executable code). But it's better that it's executable, one can know breaks faster, and update in structures are binding to both FE and BE tasks. Both sides can still mock stuff if the other side is not done.
Think about this.