Usersnap Blog
usersnap.com · Company blog · on HN since 2013
Usersnap is a visual bug tracking and feedback SaaS company, and its blog covers web development tools, SaaS, and remote team productivity.
What HN saysHN commenters mostly mention Usersnap as a tool for collecting screenshot-based user feedback, including some from users and its CEO, rather than discussing the blog.
26HN people shared it
13linked it in comments
390stories submitted
1.1Kstory points
1 year agolast shared
2013people per year2026
Most-shared posts
- 1Visual Bug Tracking: Finally Understandable Tickets12 people · 6 points · first shared 2013 · discussion on HN
- 220+ fantastic newsletters for developers4 people · 13 points · first shared 2015 · discussion on HN
- 3Top 8 SaaS Monitoring Tools for DevOps3 people · 21 points · first shared 2015 · discussion on HN
- 4What no one tells you about working in web development3 people · 18 points · first shared 2015 · discussion on HN
- 511 Productivity Boosts for Remote Web Development Teams3 people · 12 points · first shared 2015 · discussion on HN
- 6Firefox Add-ons for Developers3 people · 10 points · first shared 2015 · discussion on HN
- 7How to build a SaaS application in 20173 people · 9 points · first shared 2015 · discussion on HN
- 8Usersnap – Visual Bug Tracking2 people · 44 points · first shared 2013 · 24 comments on HN
- 923 Lessons Learned from Interviewing the World's Top Developers2 people · 35 points · first shared 2015 · 6 comments on HN
- 1012 web development blogs you should be reading right now2 people · 20 points · first shared 2015 · discussion on HN
- 1115 helpful chrome extensions every developer should know2 people · 14 points · first shared 2015 · 1 comments on HN
- 12A beginner’s guide to deploying static sites using Flightplan2 people · 11 points · first shared 2015 · discussion on HN
- 1310+ helpful GitHub hacks to immediately boost your productivity2 people · 11 points · first shared 2015 · 1 comments on HN
- 14Usersnap: Personal. Better. Faster. Meet the New Personal Lists2 people · 9 points · first shared 2015 · discussion on HN
- 157 Excellent Open Source Bug Tracking Tools2 people · 8 points · first shared 2016 · discussion on HN
What HN people wrote when they linked it
bogomil · 2014-07-01
I can recommend you to check http://usersnap.com - you can get a feedback from your peers on everything and you don't have to be alone in that task. SAAS is all about the community right?
fdorfbauer · 2014-02-11
My name is Florian, I'm one of the co-founders and CEO of https://usersnap.com
Since we're competitors, I won't add specific advice. However I'd like to encourage you to stay in business as I'm absolutely convinced that the market we're in is big enough and that the idea behind the products we're building is a great idea.
adrianmsmith · 2022-08-02
https://usersnap.com/ could be an option. - doesn't have comments on HTML elements but does allow users/stakeholders to draw on the screen and submit reports of what they've drawn e.g. if something looks wrong.
devber · 2016-06-23
I use https://usersnap.com. The screen capture + browser annotations are super easy for my clients to use. And the dashboard is pretty slick too.
caffeinewriter · 2015-02-16
[Usersnap](https://usersnap.com/) might fit your needs perfectly. I just started experimenting with it myself, but it allows users to submit visual feedback via screenshots.
volldabei95zwei · 2014-07-18
How does this product compare to http://bugherd.com/ and https://usersnap.com/ ?
grexi · 2014-03-10
You're right - every user action / step is hard for support.
We tackled this problem with Usersnap (https://usersnap.com ) - devs will get accurate information (Browser + OS version and a screenshot) directly with the bug report!
binarymax · 2025-05-19
Yes! I still want to default to accept-language, but asking is key. What is your pattern for giving the user an option? I like this article in that it rejects icons, but I don’t like how they arrive at one language for multiple regions https://usersnap.com/blog/design-language-switch/
srinathrajaram · 2017-06-14
Hey this is really interesting. Congratulations. A few questions/observations.
1. You should really be linking to - https://usersnap.com/jira that website has a lot more clarity.
2. In your pricing page you mention '10 users'. What constitutes a user?
3. If I have three projects, how would I select a project from the screenshot?
teomoo · 2015-12-04
I currently use:
- Ghostery (https://www.ghostery.com/) - analysing cookies and installed trackers on a site
- Usersnap (https://usersnap.com) - for tracking bugs and collecting feedback for our website projects
- Pocket (https://getpocket.com) - bookmarking
- Zenmate (https://zenmate.com/) - for not worrying about country blocked content
- Image downloader (https://chrome.google.com/webstore/detail/image-downloader/cnpniohnfph…
FloorD · 2013-07-18
Hi all, we've collected your additional tips for a new post on responsive design. Thanks again for your input! http://usersnap.com/blog/responsive-web-design-tips-from-the-community…
solardev · 2024-09-30
If you deploy on Vercel, the preview builds are automatic, and there is on-page commenting and discussions: https://vercel.com/docs/workflow-collaboration/comments
There are similar tools if you're not on Vercel, like https://usersnap.com/l/visual-feedback-tool
But beyond that, I don't think you should be having all the long discussions in the same place that you keep your tickets (let's say a kanban board). Have your discussions wherever you want, but keep them between the 2-3 people really involved. Then once they have an idea of what needs to change, THEN they can make a ticket for it with just some simple bullet points (linking back to the full discussion if they want).
Having everyone comment in the QA ticket directly mixes up discussion about the ticket itself and discussion about what to ticketize (which should've been done previously, outside the ticket). It's too much detail for the rest of the team to keep up with. They don't need the whole sordid history of how you got there, just what needs to be done.
In the teams I've been on, that previous discussion would happen all over the place... sometimes over Slack, sometimes over coffee at the coffee shop next door, sometimes in Figma/GDocs/Vercel comments, whatever. But once we come to an agreement, one of us writes the actual ticket without all the baggage, keeping it simple and clear.
----------
Edit: I think it really helps to have someone on the team who cares a lot about organization (and maybe even enjoys…
ashleyusersnap · 2019-04-09