IdeaSift

Web developers struggle to mock APIs reliably during local development

Frontend and AWS Amplify developers need local REST APIs and predictable API responses while building and testing apps. The evidence describes gaps in Amplify’s REST workflow, configuration that still points to the cloud, and mocking tools that do not fit Next.js server component tests. Local routing and HTTPS setup appears as an adjacent local-development pain, but is not the core problem.

For frontend and AWS Amplify developers. Mentioned from Feb 2020 to Oct 2023 on GitHub and Hacker News.

5 different people described this problem in 3 separate discussions.

Week of 2026-07-13: 0Week of 2026-07-20: 0Week of 2026-07-27: 0Week of 2026-08-03: 0Week of 2026-08-10: 0Week of 2026-08-17: 0Week of 2026-08-24: 0Week of 2026-08-31: 0Week of 2026-09-07: 0Week of 2026-09-14: 0Week of 2026-09-21: 0Week of 2026-09-28: 0
0 mentions in the last 12 weeks
Indie fit
5.0/10
Pain
6.8/10
Frequency
6.5/10
Willingness to pay
0.0/10
Momentum
5.0/10
Who pays
Professionals
Competition
Medium
Build difficulty
Medium

What people said

Quoted word for word. Follow a link to read the whole discussion.

  1. I'm currently able to run the express server locally via amplify function invoke, but automatically changing aws-exports.js and hot reloading the express server on code change does not happen through this method
    hisham on GitHub (aws-amplify/amplify-category-api)Feb 2020Asked for a toolHas a workaround
  2. Would be great to quickly run amplify mock api when you have a basic rest api with express. I don't have a GraphQL backend so mock doesn't work
Build brief

See what to build and who will buy it

  • 2 product ideas with the smallest useful version and pricing
  • 4 places to find your first customers
  • 3 more quotes from people who have this problem
  • Current workarounds, existing solutions and risks