This is entirely backwards. Don't build a general purpose API so your front end can have half the the logic outside. Just build it the way you would as if it

This is entirely backwards. Don't build a general purpose API so your front end can have half the the logic outside. Just build it the way you would as if it were local, and then hook it up to a back end with a git-like synchronization mechanism. You know, the same way you do all your own development. If you don't know how to do that, maybe you could learn that instead of arguing over REST vs GraphQL, or whether your line format should care what boxes are on the page. All I know is, it's fantastic to be able to add features to a front end, persisted in a back end, without having to write code on both sides. "What about validation??" Guess what, if users each have their own workspace, isolated and data driven, you don't need to worry about one bad request ruining your whole service.