I built this because
I needed it.

I’m Jason Gouliard. I’ve led product design teams at Google, Microsoft, Shopify, Meta, and Square. Hot Takes is the tool I kept wishing existed: real feedback on a real build, from the people steering the project.

See pricing
The problem

My teams stopped making mockups.

The prototype got better. The feedback got harder to provide and collect.

Designers on my teams skip Figma now. They go straight to code: SwiftUI, AI-assisted, running on a real phone by the end of the week.

The work is further along than a mockup ever was, and it is running on the device it was made for. What went backwards is everything that happens after you hand it to someone.

There was no file left to comment on.

Stakeholder reactions came back as Slack threads, camera-roll screenshots, and hallway summaries of something a VP said. Nothing was tied to the build, the screen, or the person who said it.

By the time a reaction reached the designer it had lost the one thing that made it useful: what was on screen when someone had it.

I wanted Figma-quality feedback on the compiled app. No tool did that. So I built it.

Jason Gouliard, founder. Every screen on this page is the shipping product, captured inside a real build.

What it’s for

One job, on purpose.

Hot Takes is not a design tool, a prototyping tool, or a research platform. It does one thing: it gives your stakeholders an easy way to deliver feedback from within your app.

Inside the real build

Captures happen while a stakeholder is using your build on their own device. Not a mockup, not a browser stand-in. One line of Swift puts the capture tools inside the app you already ship, simulator included, and there is nothing for a reviewer to install.

Tied to a verified person

Every take is attributed to a real, email-verified stakeholder. No anonymous drive-bys, no guessing who meant what. Reviewers come with the plan: 2 per project on Free, 5 on Starter, 25 on Pro, and anyone you want reading the gallery is free.

One shared gallery

Screenshots and narrated recordings land in one per-project gallery instead of scattering across Slack, texts, and camera rolls. Recordings carry live voiceover, so you hear the thinking and not just the conclusion.

A take marking up the canvas screen of a prototype
Dana Rivera
Jul 19Screenshot
A screen recording of the generate flow, with markup drawn over the running app0:58
Miles Kwon
Jul 18Recording
A take marking up the packages screen of a prototype
Priya Anand
Jul 17Screenshot

Three takes from one project, in the same card the gallery gives them: who sent it, when, and which kind.

What you get back

One project, one place, grouped by screen.

Takes arrive and file themselves next to the others from the same screen, so a project reads as a storyboard of your prototype in flow order. Nobody sorts or renames anything.

The Hot Takes project page in storyboard view: screen groups with new-take badges, project details, and recent activity
Storyboard viewTakes auto-grouped by screenFiltersBy reviewer, type, or tagUnsortedTakes that can’t be auto-grouped park here
Storyboard view
  1. Storyboard view Takes auto-grouped by screen
  2. Filters By reviewer, type, or tag
  3. Unsorted Takes that can’t be auto-grouped park here
Where it fits

The tools you already use are good. Keep them.

Most of these are excellent at their own job. None of them do this one: reach a native build on a device without asking anyone to install something separate.

ToolWhat it’s built forReaches your native build, on a device?
Hot TakesAnnotated screenshots and narrated screen recordings from inside a running iOS prototype, tied to verified stakeholders, in one gallery.Yes: that’s the whole job.
Figma and Figma commentsDesign files and web-based, clickable prototypes.Not directly: comments live on the file or the web prototype, not on a compiled app running on a phone.
MazeStructured usability studies, moderated or not, via Maze Participate, a dedicated mobile app for running tests on-device.Not directly: participants install a separate app and run a structured study in it, not your own build.
UseberryModerated and unmoderated usability studies against clickable prototypes.Not directly: built to study a prototype running in a browser, not a native build.
UserTestingModerated sessions with testers recruited from a panel.Different job: feedback from a recruited panel, not from your own named stakeholders on your own build.
Raw TestFlight feedbackApple’s built-in screenshot capture, forwarded to App Store Connect.Yes, but with none of the tooling around it: no video recording or annotations, no auto grouping of feedback, no gallery, no team flow.
LoomAsync screen recording of anything on your computer or device.Not in context: recorded outside the app, with no device or app metadata attached to what you’re watching.

Nothing here replaces the tool above it. Hot Takes starts where they stop: the moment the work is compiled and on somebody’s phone.

Put it in your next build.

One line of Swift. Your stakeholders’ takes,
in one place.

See pricing