Summary

Ray introduces Mockoon, a desktop Mock API tool, and explains why frontend developers should use mock APIs to develop in parallel with backend work. When backend APIs won’t be ready for 5-6 days but the frontend also needs 5-6 days, waiting for the API means missing deadlines. Mockoon allows frontend devs to work against API specifications immediately, without waiting for actual backend implementation.

Ray 介紹 Mockoon 這個桌面 Mock API 工具,並說明前端開發者為何應使用 Mock API 並行開發。當後端 API 需要 5-6 天才能完成,前端同樣需要 5-6 天時,等待 API 意味著趕不上截止日期,Mockoon 讓前端可以立即依照 API 規格開發,無需等待實際後端。

Key Points

  • Mock API solves the parallel development problem: frontend and backend can work simultaneously with an agreed-upon API spec
  • Ask backend for API spec first (URL, method, request params, response shape), then create mock based on spec
  • Mockoon is a desktop app (cross-platform) that runs a local mock HTTP server
  • Unlike Postman mocking (cloud-based, requires account), Mockoon runs entirely locally
  • Mock endpoints can be configured with status codes, response bodies, delays, and dynamic response rules

Insights

The parallel development pattern is a critical productivity technique in any multi-person project. The constraint that “API integration issues will always exist” (even with mock APIs, you’ll hit discrepancies when real backend is ready) is honest — mock APIs reduce the delay but don’t eliminate integration work. Mockoon’s local-first approach is particularly useful in environments where cloud mocking services are blocked or where latency would affect development experience.

Connections

Raw Excerpt

如果你知道如何使用 Mock API 的話,你就可以請後端優先先開出 API 規格給你,然後再依照 API 規格轉換成 Mock API,這樣你就可以在切完畫面後,馬上接著開始串接 API。