Hi HN, I’m Pavel from FiredAPP Development, the team behind Tentomushi.
We built this side project to reduce the back-and-forth that follows vague bug reports. A user can record their screen or upload an existing screenshot or video showing the issue they want to report. AI drafts a title, description, and reproduction steps. The reporter reviews the result and submits it to one configured ticketing tool. Reports can also be translated for teams working across languages.
You can also create a unique link for your product through which your clients or end users can report problems they encounter with your application. They don’t need to create an account. They simply review the result and submit it.
There is currently no free tier, free trial, or public demo. As this is our side project, we are not able to provide anything for free. Paid plans start at €9/month and include a 30-day partial-refund guarantee, subject to the usage and fee deductions described in our terms.
I appreciate any feedback on the workflow and positioning, as well as what kind of demo or trial would make the product worth testing for you.
One challenge I've seen is that users often submit recordings without enough context. They show what happened, but not what they expected to happen. Have you considered prompting users for the expected behavior before generating the report?
Good point. Users can currently add optional context before AI processing, which they can use to describe the expected behavior. However, we don’t explicitly prompt for an "expected outcome", so it may be easy to overlook or omit. It might be worth changing the wording around the additional context the user can provide. Thanks for the feedback.
Hi HN, I’m Pavel from FiredAPP Development, the team behind Tentomushi.
We built this side project to reduce the back-and-forth that follows vague bug reports. A user can record their screen or upload an existing screenshot or video showing the issue they want to report. AI drafts a title, description, and reproduction steps. The reporter reviews the result and submits it to one configured ticketing tool. Reports can also be translated for teams working across languages.
You can also create a unique link for your product through which your clients or end users can report problems they encounter with your application. They don’t need to create an account. They simply review the result and submit it.
There is currently no free tier, free trial, or public demo. As this is our side project, we are not able to provide anything for free. Paid plans start at €9/month and include a 30-day partial-refund guarantee, subject to the usage and fee deductions described in our terms.
I appreciate any feedback on the workflow and positioning, as well as what kind of demo or trial would make the product worth testing for you.
One challenge I've seen is that users often submit recordings without enough context. They show what happened, but not what they expected to happen. Have you considered prompting users for the expected behavior before generating the report?
Good point. Users can currently add optional context before AI processing, which they can use to describe the expected behavior. However, we don’t explicitly prompt for an "expected outcome", so it may be easy to overlook or omit. It might be worth changing the wording around the additional context the user can provide. Thanks for the feedback.