So instead of managing state on the client, you manage state on the client and the server? That doesn't seem like an improvement, even if it saves you from having to build yet another API.
Yeah that is the crux of most modern three-tiered architectures (client server database) these days. We're working on simplifying this with a new concept: a full-stack database. If you run an identical query engine on client and server and then sync data between them, a client can just write a normal query on the client and you get an optimistic response instantly from a local cache and then later a response from the…
But more stuff like this is always welcome!