Home
Starting Up
Case Studies DB
Products
Ideas DB
Vibe Coding Tools
Subscribe to IH+
Starting Up
Case Studies
Ideas DB
Products DB
Join
2
Likes
0
Bookmarks
3
Comments
Report
A Developer's Perspective: The Pain of Requesting Screen Recordings and Screenshots from Users
by
Anurag
https://www.kanurag.com/screen-recording/
Trending on Indie Hackers
6 weeks solo, 2 rejections, finally live but nobody told me marketing would be this hard
137 comments
Building ExpenseSpy solo, no funding — launching June 17 on iOS & Android
59 comments
I spent more time setting up cold email than actually selling. Here is what fixed it.
32 comments
I just wanted to taste AI coding tools. A week passed.
21 comments
I built a PDF API because every team I know has a haunted corner of their codebase they never want to open
15 comments
Building LinkCover – Day 3: Payment is live. No more building, time to sell.
15 comments
As a a developer, I never asked a customer for a screenshot or a screen recording. I saw it as my job to be able to figure out what happened and replicate the issue.
Even asking something simple like what browser are you using has been too much.
so you are ok to give 'x' number of hours instead of using some tool that will make your life easy?
Yes.
I'm not saying I wouldn't use a tool that would make my life easier. I CANNOT live without sentry. To me its important that its not visible to the user.
I would rather spend X debugging than spend Y talking to users. Even if X is substantially bigger than Y.
I could for sure see my customer support team using something like this though. They can walk the customer through it, I get the screenshot/video but don't need to talk to the customer.
Another way I can see this working for me as a developer is if I can enable it for the customers that I know are being affected by a bug.
For example if I know this happens only to customers that are in a city:
I know this is a contrived example.