Introducing myself — building a small tool to reduce QA ↔ Dev back-and-forth

Hey Product Hunt 👋

I’m a mobile developer with 6+ years of experience, mostly working with Flutter across mobile and desktop.

Over the years, I kept seeing the same issue repeat across teams:
QA reports a bug, developers can’t reproduce it, and a lot of time is lost just trying to understand context.

On top of that, QA often has to jump between multiple tools just to create a single task — screen recorder, screenshot tool, notes, issue tracker — which breaks flow and still leaves gaps in information.

So I decided to start building a small cross-platform utility (macOS, Windows, and mobile) focused on making bug reporting clearer and faster for both QA engineers and developers.

To be clear, I’m not building another task or issue-tracking tool.
The goal is to reduce the friction before a task is created, by capturing better context upfront.

Right now, I’m early and intentionally keeping the scope small.
I’m focusing on one core capability: capturing the screen and automatically attaching useful context to reduce follow-up questions.

I’m not launching yet — just sharing early progress and learning in public.

If you’ve worked in QA or development teams:

• What’s the most frustrating part of bug reports for you?

• What context do you always wish you had upfront?

Would love to learn from this community 🙏