|

Making feedback more contextual

Floop Cover

OVERVIEW

Giving feedback on live websites sucks. It's a mess of screenshots, long messages, and endless Loom recordings. Floop fixes this by letting you annotate feedback directly on any live site. Stop explaining context and start flooping clear and quality feedback.

ROLE

Team of one: Research, design and implement end-to-end platform

TOOLS

Figma, FigJam, Lovable (MVP), Cursor, Antigravity, Claude Code

Floop Cover 2

Talked to 25+ designers. Context problem everywhere.

WHAT REVIEWERS DEAL WITH:

Screenshot. Crop. Annotate. Paste into a shared doc. Write a paragraph explaining which section of which page you're talking about. ~30 minutes and 3-4 tools just to say what you could point at in 2 seconds on a call.

WHAT REVIEWEES DEAL WITH:

A shared doc full of cropped screenshots you have to match back to the actual page. Or a Loom recording that seems great — until you have to scrub through it, take notes on timestamps, and when you reply, you're back to explaining context all over again.

Dashboard
Different ways people explain context for feedback.

Built an early prototype with Lovable and tested with 15 designers.

INTERACTION ITERATION:

While giving feedback, clicking does two things: browsing and commenting. Toggle button was too much friction. Ctrl toggle meant pressing Ctrl again after every comment. Ctrl hold-to-comment solved it.

MENTAL MODEL ITERATION:

V1 assumed you're either a reviewer or a reviewee. Turns out everyone wants to be both.

Micro-animation to show the comment mode.
Old dashboard
Old dashboard with comments without contexts.

Shipped core flows with Cursor, Claude Code and Antigravity.

Flooping feedback on live websites
Dashboard
Creating a floop link to give feedback to a live website
Give feedback modal
Creating a floop link to request feedback to a live website
Share floop
Sharing feedback to others
Visual cue to know which element is selected

Feedback time dropped from 30 minutes to 10 minutes.

30 designers, same task: give feedback on a portfolio. Half did it their normal way. Half used floop.

TRADITIONAL
30 min

3–4 tools · paragraphs of context

FLOOP
10–15 min

1 tool · feedback pinned where it belongs

STATS
  • 50+ early users, all organic
  • 24 active beta testers
  • $2,500 IU scholarship
  • $0 spent on marketing

WHAT I'D DO DIFFERENTLY

Next time, I'd find a developer I trust and build together. AI tools gave me control over every small decision, but a trusted dev partner plus AI would mean speed, quality, and someone to challenge my technical choices.

GO BACK