Flaw Snap

A lightweight visual bug reporting and website feedback tool for capturing, annotating, and sharing issues.

[Flaw Snap @flawsnap]

The Flawsnap Chrome extension is live.

Report bugs on any site, no code: box it on a screenshot or record the tab. It lands on your board with the page, browser and, if you allow it, console errors and failed requests.

Chrome, Edge, Brave:
https://t.co/VIOwobCyQW

[Flaw Snap @flawsnap]

https://t.co/JjeyMFN3me is a good tool, and for many teams the right one.

I compared the alternatives for small teams and native mobile apps, with prices from each vendor's own pages. Disclosure: I build one of them (Flawsnap) and list its limits too.

https://t.co/SsPaxOIBtg

[Flaw Snap @flawsnap]

"Discount codes don't work, please fix asap."

A good bug report lets someone reproduce the problem without asking you anything. 7 habits that get you there, with a before/after of the same bug:

https://t.co/eXBJK9TLOD

[Flaw Snap @flawsnap]

"I clicked Pay and nothing happened."

Nine times out of ten, the explanation is already in the browser console, in red. The person reporting the bug never opened it.

A field guide to the 7 console errors behind most "the button does nothing" reports:

https://t.co/Ec0oC9r9Le

[Flaw Snap @flawsnap]

Our Chrome extension was rejected for "remotely hosted code", yet it loads nothing remote.

It bundled our widget's code, which can inject a script. Review checks what a package could do.

Fix: strip it at build time, fail the build on 8 patterns.

https://t.co/o63Gi4FMge

[Flaw Snap @flawsnap]

Day 2 of selling Flawsnap:
✅ Chrome extension live on the Web Store (one rejection first)
✅ 13 cold emails to agencies, each pointing out a real bug on their site
✅ First meme reel on Shorts, IG, FB and TikTok
🙋 1 sign-up

Paying customers: 0. Replies: 0. Building in public.

[Flaw Snap @flawsnap]

First version, built by a tiny team. If something's confusing or broken, reply here and tell me. That's the most useful thing you can send right now.

Setup guide: https://t.co/m9d2xLP89B

[Flaw Snap @flawsnap]

The Flawsnap Chrome extension is live.

Report bugs on any site, no code: box it on a screenshot or record the tab. It lands on your board with the page, browser and, if you allow it, console errors and failed requests.

Chrome, Edge, Brave:
https://t.co/VIOwobCyQW

[Flaw Snap @flawsnap]

Honest limits:
• it signs in with a Flawsnap account (7-day trial, then $9 or $19/mo per org, unlimited members)
• it's for your team; customers use the widget, no account needed
• Chromium only for now, no Firefox or Safari

[Flaw Snap @flawsnap]

Agency folks: what's the worst client bug report you've ever received?

I'll start: "the website is broken", plus a photo of their monitor taken on a phone.

[Flaw Snap @flawsnap]

Flutter devs: how do your testers report bugs today?

Screenshots in WhatsApp? A Google Doc? 🙃

Our Flutter package lets them circle the bug in the app, and you get the screenshot, device info and logs in one report.

https://t.co/KmtDS0HHq1

[Flaw Snap @flawsnap]

@ASPnix Matching the server fixes half of it. The other half is the user's machine: an old Safari, an extension injecting scripts, 125% zoom, a flaky corporate proxy.

You only close those once you capture the reporter's browser and console at the moment it broke.

[Flaw Snap @flawsnap]

@kamilbaranek_ Honestly that's the right number to call. The agency that built it is the one who'd lose sleep over a 404 their client hasn't even noticed yet 😅

[Flaw Snap @flawsnap]

@dereklee1029 The "let me review and redact before sending" part is underrated.

People share way more context when they can see exactly what's attached. Show them the screenshot and logs before submit, with an easy way to blur anything sensitive, and the reports get much better.

[Flaw Snap @flawsnap]

Day 1 of selling Flawsnap:

✅ Stripe is live
✅ Intro video out
✅ First reel on Instagram

Paying customers: 0. Yet.

It's a visual bug reporter for websites and Flutter apps, from $9/mo. I'll share every number here as it moves.

[Flaw Snap @flawsnap]

@bardonadam @zernio Love this. One addition that's helped us: have the agent attach the exact call it was attempting (params redacted) plus the error it got back.

"missing_feature: can't filter by date" becomes way more actionable when you can see the request that failed.

[Flaw Snap @flawsnap]

@aurem_live The one people forget most is the network tab.

Half the "login is broken" reports we see turn out to be a 401 or a CORS error that never shows on screen. Paste the failing request too, and the fix usually takes minutes, not hours.

[Flaw Snap @flawsnap]

@thecodenamev @sfrubyconf Splitting user-agent tools from maintainer tools is a really clean idea.

One thing we've seen building in this space: agent-filed bugs get far more useful when they carry the page URL, console errors and the failing request. Any plans to attach context like that?