Your players know where the fun slows down.
The menu they keep reopening. The option they can’t find. Give your players a simple way to show what would make the next version feel better.
Choose your loadout
“Could I compare my gear without reopening each item?”
The game works. The repeated menu switching still gets in the way.
Illustrative walkthrough · No feedback is sentA small team can’t play from every perspective.
Your players can. Keep their suggestions and visual context together, then choose changes that support the game you want to make.
- 01
Hear from your own players.
Share a feedback link in your menu, community or playtest notes. Players don’t need an account.
- 02
See the moment that matters.
Screenshots and short clips put the confusing menu, unclear tutorial or missing option in context.
- 03
Protect your development time.
Read feedback against your intended experience before adding another feature to the plan.
Show the moment. Keep the context.
A note, up to two screenshots or short clips, and the original words together. Users can mark a screenshot and review what they share before sending.
Feedback stays private to the project owner. A private status link lets the person who shared it follow progress. Recording starts only when they choose it.
A small start, with clear expectations.
Will this work with my product?
For indie studios, browser games, prototypes and teams running their own playtests. Native games use a hosted link. Patchkind does not recruit testers or include Unity or Unreal SDKs, heatmaps or passive session replay.
What does the beta include?
Feedback collection, visual attachments, product direction and owner review. Connect your assistant to read the original notes and screenshots, or download an approved brief with its images. Built-in dashboard AI and video analysis are not enabled.
What happens after I request access?
The invited beta is free. We review requests and contact teams we can support. Invitations are manual. We’ll confirm available features and any terms before you join; there is no self-serve paid plan yet.
Add feedback to your next playtest.
- Create your project. Once invited, open your workspace and add the product’s name, website and direction.
- Choose a button or a link. In Connect, copy the instructions for your coding agent. A browser game or website can load the widget once; a native game or app can open the hosted feedback link.
- Verify the whole delivery. Open it from your product, send a labelled test with a screenshot, then check the note and image in your Patchkind workspace.
People can upload an image on mobile. Screen capture depends on the browser’s support and permission picker. Numbered screenshot pins travel with the original report and the downloadable agent brief.
Build the next version with more player perspective.
Tell us what you’re building. Start with the feedback you wish you had.