To me it's a weird way to go about this decoupling. Another way is you can just keep your own view-model client side and abstract the backend data with that.

To me it's a weird way to go about this decoupling. Another way is you can just keep your own view-model client side and abstract the backend data with that. FFBs and GraphQL is a way to tightly couple to a backend system and then have that backend system loosely coupled. I guess its all 6 of one, half-dozen of the other, but I usually prefer to just handle things client side. You can maybe get less data transfer optimization but that's down the road from the fast development stage, anyway.