Skip to content

A visual feedback tool for reviewing what your team ships

Updated

Midge is a visual feedback tool for product managers who review web apps before and after release. You capture an annotated screenshot or a short screen recording of any page in Chrome, add a title and a sentence of context, and share one link. Developers who open it also get the console logs, network requests and browser details behind what you saw, so your feedback turns into a fix without a meeting.

Midge is free: unlimited recordings, videos up to 15 minutes, and no watermark. Teams and folders are free too, so the whole product group can use it.

Feedback that shows instead of describes

"The spacing on the pricing card looks off" can mean five different things. A screenshot with a box around the card and a label that says "16px gap here, 24px on the other cards" means one. Visual feedback removes the interpretation step.

Annotated screenshots

Capture the visible area or drag to select a region, then add:

  • arrows to point at the exact element,
  • boxes to frame what should match,
  • a pen for quick circles and underlines,
  • text labels for the expected value,
  • blur for any real customer data on the page.

See the screenshot page for details.

Short videos

Some feedback is about flow, not pixels: an onboarding step that feels slow, a modal that closes too early, a transition that jumps. Record a tab, narrate with the microphone if you like, and stop. A 30-second video with your voice saying "I expected to land on the dashboard here, not on settings" is clearer than a paragraph. See the screen recorder.

Shareable links

Every report is a link. Paste it into the ticket, the release channel or the review doc. You decide who can open it:

  • Anyone with the link, useful for agencies, contractors or stakeholders outside your workspace,
  • Workspace members only,
  • Only me, while you are still collecting thoughts.

Feedback developers can act on

This is where Midge differs from a general screenshot or video app. Every recording includes console logs, network requests, user actions and device info. You do not need to understand them. The developer does, and they are already in the report.

Suppose you notice that the "Upgrade" button on staging shows the old price. To you, it is a copy issue. The attached network log shows the plans API returned last quarter's price list, which makes it a backend cache issue. The developer sees that in the first minute instead of fixing the wrong layer.

Sensitive data stays out of it. Passwords, card numbers, tokens and cookies are redacted in your browser before anything leaves your device, which matters when you are testing on production with your own account. More on the redaction page.

How product teams use it

Release review. Before a release, walk through the new flows on staging and capture anything off. Put the reports in a folder named after the release, so the team has one list to work through.

Acceptance checks. When a ticket moves to "ready for review", check it against the acceptance criteria and reply with a Midge link for anything that does not match.

Stakeholder feedback. When a sales lead or an executive reports "something weird on the checkout page", ask them to record it. Their recording carries the technical context they could never describe.

Bug reports from the field. When you hit a bug yourself in production, record it before you lose the state. If you were not recording, instant replay can save the last 30 to 120 seconds, if you turned it on for that site.

Writing feedback that gets acted on

Short, specific reports get fixed first. A good pattern is one issue per report, a title that names what is wrong, and one line on what you expected. Our bug report examples show this side by side with vague versions, and how to report a bug covers the basics for non-engineers.

What Midge does not do

Midge captures and shares feedback on web pages in Chrome, and on any app with Midge for Mac. It does not comment inside design files, and it does not replace your roadmap or ticketing tool. It does connect to them: with Jira, Linear, GitHub Issues or Slack connected by a workspace admin, one click on a report opens an issue or posts to a channel with the link, the AI summary and the steps to reproduce. See integrations. Asana, Trello, ClickUp and Notion are not supported natively; a signed webhook can bridge them. For customers and clients, recording links let them send a screen recording from their browser without installing anything.

If a developer ever asks you for a HAR file instead of a recording, our free HAR sanitizer removes cookies and tokens from it in your browser before you send it.

Frequently asked questions

Do I need to be technical to use Midge?
No. You take a screenshot or record your screen and share a link. The technical details developers need are captured in the background without any setup.
Can I give feedback on designs in Figma?
Midge works on web pages open in Chrome, such as a staging site or a production page. For comments inside a design file, use your design tool's own commenting.
Can people outside my team view the feedback?
Yes, if you choose. Each report can be shared with anyone who has the link, only with your workspace members, or kept private to you.
How much does it cost for a whole team?
Nothing today. Midge is free, including teams, folders and unlimited recordings. Paid plans may come later.