Developers struggle to test apps outside standard browser workflows
Developers need automated checks for browser and app behavior, but standard testing workflows can break down in remote or containerized workspaces and with less conventional targets such as Flutter Web, Electron apps, extensions, and iframes. They also report slow test suites and limited ways to record or observe test runs and reuse a browser session. The signals span different frameworks and targets, so a generic runner would not solve every case.
For frontend and app developers maintaining automated UI tests. Mentioned from Sep 2016 to Sep 2026 on Bluesky, product forums, GitHub, Hacker News and Stack Exchange.
47 different people described this problem in 40 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 6.0/10
- Frequency
- 10.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
At my company we have a small project where we are running the equivalent of 6.5 hours of end2end tests daily using playwright. Running the tests in parallel takes around half an hour
There's no way for Claude to see a running app the user has open, even when the user wants to share it. Today the workarounds are screenshots, paste, WebFetch (no auth, no JS), or driving headless Playwright via Bash — all clunkier than what Copilot agent mode now gets for free
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 6 places to find your first customers
- 49 more quotes from people who have this problem
- Current workarounds, existing solutions and risks