Mock Data Strategies That Scale into Real APIs

Using static in-repo data during the first delivery phase reduces moving parts and keeps deployments simple. The mistake is wiring that data directly into every page.

A thin data-access composable creates a stable interface for fetching lists and detail records. Today it can return local arrays, and later it can call useFetch or a server route.

That separation keeps UI code steady while the delivery model changes underneath it.