Bug reports your AI agents can fix.
Report bugs that tell the whole story, the first mile of every fix.
Start freeWatch a report write itselfCreate account
The picture, marked up
Private fields already blurred.
The last 30 seconds
Sign up → Name → Email → Password → Continue (nothing happened)
The scenario, in plain words
- Given
- signed out, on Create account
- When
- name, email and password typed, then Continue tapped
- Then
- nothing happened. Expected: the Welcome screen
The phone and the app
Where it most likely lives in the code
lib/screens/signup_screen.dart:142 · ContinueButton, found by the widget's name
A test draft
What a bug report usually leaves out.
Writing a good bug report is hard. Even careful testers leave things out, and the fix waits while someone asks.
“I tapped something and it broke.” Which taps, and in which order?
By the time the report is written, the last 30 seconds are gone.
Text size, dark mode, language, network, battery. Nobody thinks to write them down.
A screenshot shows what went wrong, not which part of the app drew it.
What Pro writes into every report.
The phone only collects. The bugsTweet service writes these parts, so your agent can start on the fix at once.
Given, When, Then. The agent turns it into a test for every later build.
- Given
- signed out, on Create account
- When
- name, email and password typed, then Continue tapped
- Then
- nothing happened. Expected: the Welcome screen
“Were you signed in?” The tester taps the answer on the phone. No developer in the middle.
When the build with the fix lands, the tester gets the retest card: which screen, the old picture, the steps.
A slider over the last 20 seconds: the picture, the screen and the app's state at each step.
A short speed test runs when the report is sent.
- Network
- Wi-Fi, 24 Mbit/s
- Battery
- 41%, power saving
- Storage
- 1.2 GB free
- Memory
- 68% used
- Heat
- normal
Before sending, bugsTweet checks for the same bug and offers to add to it.
One line in the app lets the report say what the app knew.
Hold, do the thing, release. Free plans keep the clip on the phone to watch; Pro puts it in the report.
Example content. Every part above is live in bugsTweet today, made by the service for Pro.
Free for every tester.
Hold the bird and the menu opens. Everything here is free, always.
Before and after, compared, and said in words.
Shake the phone to capture, hands busy or not.
After a normal phone screenshot, bugsTweet offers to report it.
Arrow, box, pen, highlight, blur, text, stamps, crop.
Ruler, color picker and contrast check, for design bugs.
The whole page, stitched into one tall picture.
Passwords and private fields are blurred before anything leaves the phone.
The old picture, the screen, the taps; capture again and compare.
A short summary before sending; see the full issue text.
How it works
One line. Your store app never contains it.
Mark up the screen, add a note, send.
When the fix lands, the tester retests from the phone.
issue #12 → fixed in build 31 → retested ✓
Your code stays yours.
bugsTweet never gets access to your app's code. Reports go to a separate, private reports repository, and there the bugsTweet service allows only its own actions: post a report, comment, close or reopen, add a picture.
Free to report. Pro for the whole story.
Every tester can report bugs for free, always. Pro adds what nobody can write down.
See pricing