A few years ago, I was working on a project where the frontend team was blocked for almost two weeks.
Not because the feature was complicated.
Not because the requirements were unclear.
Not because there was a production issue.
We were waiting for an API.
The endpoint wasn't ready.
Every standup sounded the same:
"Frontend is done except for integration."
"Backend is still working on the API."
"We'll test once the API is available."
Everyone was busy, but nobody was moving forward.
The frustrating part is that this is completely normal.
Most teams build software in parallel:
- Product defines requirements
- Backend builds APIs
- Frontend builds screens
- QA prepares test cases
In theory, everyone moves together.
In reality, one missing endpoint can slow down an entire workflow.
So what happens?
Developers start creating temporary fixes:
- Hardcoded JSON files
- Fake responses inside React components
- Local Express servers
- Postman collections shared over Slack
These work for a day or two.
Then requirements change.
The fake response doesn't match the real API anymore.
Someone updates their local version.
Someone else forgets.
QA tests against different data.
A bug appears.
Nobody knows whether the problem is in the frontend, backend, or the mock.
I've seen teams spend more time maintaining temporary workarounds than building the actual feature.
The real problem isn't that the API isn't ready.
The real problem is that development stops when it shouldn't.
A frontend developer should be able to continue building.
QA should be able to continue testing.
Product should be able to continue reviewing progress.
Even if the backend service doesn't exist yet.
That's why I've become a big believer in treating API mocking as infrastructure rather than a temporary development trick.
Instead of creating mocks on individual laptops, create a stable endpoint that everyone can use:
- Frontend uses it
- QA uses it
- Demo environments use it
- CI pipelines use it
One URL.
One response.
No environment drift.
No "works on my machine."
No waiting.
The funny thing is that most engineering teams don't lose time because of difficult technical problems.
They lose time because teams depend on each other.
And every dependency becomes a bottleneck.
The next time someone says:
"We're blocked because the API isn't ready."
Ask a different question:
"Why does development have to stop?"
Top comments (0)