I did this on a client project recently, but ended up moving away from it. I Found it falls down when you have different devs working on the same features from different ends. Instead, I used JSON files that the back end would just serve from the routes I expected.
Firstly, it provides a clearer and more obvious contract with the back end, one that you can see in the network traffic.
Also, when the endpoint is actually implemented on the API, it all Just Works. There's no intermediate step of pulling out the mocks and letting the real data flow through. It also provides a simple smoke test path during development of the endpoint.
Comments
I did this on a client project recently, but ended up moving away from it. I Found it falls down when you have different devs working on the same features from different ends. Instead, I used JSON files that the back end would just serve from the routes I expected.
Firstly, it provides a clearer and more obvious contract with the back end, one that you can see in the network traffic.
Also, when the endpoint is actually implemented on the API, it all Just Works. There's no intermediate step of pulling out the mocks and letting the real data flow through. It also provides a simple smoke test path during development of the endpoint.