Scheduling user interviews for early product design feedback is difficult. Time conflicts, no-shows, and context switching makes for a poor experience. The realization that stuck with me is that most users are already inside your product. That's where feedback should happen too. I built Reactions. Users explore concepts (Figma prototypes, videos, mockups) right inside your app and leave feedback on their own time. No scheduling, no Zoom, no forcing anyone to switch contexts.
Scheduling user interviews is frustrating for everyone involved, and I've been on both sides of it.
I've emailed users a Calendly link and then sat alone on a Zoom call after a no-show. I've also been the user on the other end, stopping what I was doing to find a slot on someone else's calendar just to give a few minutes of feedback. The whole thing feels heavy for something that should be simple.
Meanwhile, I kept watching good prototypes die in a Figma file because "we didn't have time to run a study." Nobody schedules a formal interview for a 3-day feature, so those features just ship on a hunch or die without feedback.
The realization that stuck with me: most users are already inside your product. That's where feedback should happen too.
So my hypothesis was that async, in-context reactions on early designs (Figma prototypes, Loom videos, mockups) could fill that gap. Cheaper than interviews, faster than a survey, and closer to the real thing than either. I built a tool around it (https://getreactions.app) and have been dogfooding it on itself. Users explore early concepts right inside the app and leave feedback on their own time. No scheduling, no Zoom, no forcing anyone to switch contexts.
Eat Your Greens