SnagFrogThe short answer: sort every open report and error into the problem behind it, count the people each problem reaches, and fix from the top. Five reports about a frozen timer, a wrong total and a crash after sleep are often one bug. SnagFrog Themes finds those groups for you.
Why read feedback by theme?
- People describe the same bug in different words, so a list of reports hides how big a problem is.
- Errors your app captured on its own belong to the same problems, but nobody wrote them up.
- A count of people turns "what do I fix today?" into a ranking.
Step 1: Collect reports and errors
Themes work on what SnagFrog already has: reports from the widget, the Mac app or the Godot game, and captured errors. Contact us for a workspace if you don't have one.
Step 2: Group the feedback
Open the app, then Feedback → Themes, and press Group feedback. Open reports and errors without a theme are sorted into the themes you have, or into new ones. Later, press Group new feedback to sort only what came in since.
Questions, closed reports and duplicates are left out; a duplicate's reporter still counts for the original's theme.
Step 3: Read the list from the top
Themes are listed with the ones that reach the most people first. Open one to see its reports and errors, rename it, or take out an item that doesn't belong.
Step 4: Fix it, then resolve the theme
Hand the top theme to Claude: "fix the timer theme in HourSlip and notify the users". See how to fix bug reports with Claude Code. When the fix is out, open the theme and press Resolve. Its reports and errors keep their own status, so publish the release to close the reports and tell the people who sent them.
Questions
How do I decide which bug to fix first?
Fix the problem that reaches the most people, not the report that shouts loudest. Group reports and errors by the problem behind them, count the distinct people in each group, and start from the top. SnagFrog Themes does the grouping and the counting.
How are people counted?
Everyone who reported a theme counts once, by email address, including the reporters of duplicates. Each time one of its errors happened counts as one more, because errors don't say who ran into them. Ignored errors don't count. The number is an estimate, good for ranking.
Does grouping use AI?
Yes. Grouping uses the workspace's monthly AI budget. You can also ask Claude Code to do it over MCP: "group HourSlip's feedback into themes".
What is the difference between a theme and a duplicate?
A duplicate is the same report sent twice, and is merged so one reply reaches everyone. A theme is one problem behind several different reports and errors, such as "timer doesn't resume after sleep" reported as a frozen timer, a wrong total and a crash.
Related guides
All 21 guides, from an idea to a launched app.
Contact us · More guides · Docs · Compare with other tools · Changelog