I’m a frontend developer and one thing that always bothered me on client projects was the feedback process.
Clients would send things like:
“Make this button bigger”
“Change this section”
“Use another image here”
…but the feedback would come through WhatsApp, screenshots, email, or random messages, so half the work was figuring out what they were actually referring to.
I recently built ClientPin to solve this.
The idea is simple:
Client opens the website ** → **clicks the exact element → leaves a comment → developer gets the page, screenshot, browser context, and feedback in one place.
Clients don’t need to create an account just to leave feedback.
It is launched recently and have a try.
Thanks
Top comments (4)
No-account feedback for clients is the right call; asking them to sign up is where these tools usually lose the client. The hard part I'd test early is what happens to a pin after you redeploy. With Tailwind or CSS-module class names, the selector a comment was anchored to often doesn't exist on the next build, and the pin silently floats to the wrong place or disappears. Storing a few fallbacks (the element's text, its position among siblings, and a cropped screenshot) and marking a comment "element changed since this was left" keeps old feedback honest. Also worth capturing the viewport width with each comment, since "this button is too small" from a phone and from a laptop are two different bugs. How are you anchoring pins today?
hey Mythex,
This is a really useful edge case. Today ClientPin saves a selector and the element's text, along with its page position, viewport dimensions, and a screenshot. but the visible pin is currently placed using the saved coordinates, we don't yet re-anchor it to the element after a redeploy.
So you're right like layout changes could leave an older pin in the wrong place.
I like your suggestion to use multiple signals to find the element again and flag it when the match is uncertain, rather than silently pretending the pin is still accurate. capturing the viewport already helps us reproduce mobile vs desktop issues.
This is exactly the sort of thing we want to fix early.
Thanks alot for calling it out! 🤘🏻
The mess usually comes from two things: feedback arriving in five channels, and feedback that's too vague to act on ("the hero feels off"). For the second, what helps is replacing the open "any feedback?" email with a short structured form per review round: which page, what's wrong, what would "right" look like. I built chatform.in for this, a conversational form that asks a follow-up when the answer is vague, so "make it pop" turns into something you can ship. For pinning comments to elements, a visual tool is still the better fit; the two solve different halves.
요소를 직접 클릭해 의견을 남기게 한 점이 좋네요. 댓글 위치를 저장할 때 화면 폭과 시안 버전도 함께 묶어두면, 재배포 뒤 레이아웃이 달라졌을 때 어느 상태의 피드백인지 더 정확히 확인할 수 있을 것 같습니다.