1–10 of 61 posts
I want to get away from creating tickets or sending emails highlighting UX concerns. This is cumbersome and not very transparent or collaborative.
Does a tool like this already exist?
Emailing an annotated screenshot or attaching to a JIRA seems better because it's more consistent and blends with other processes. What should happen when webpages content changes or goes defunct? Now you're also creating an archive.org... and on and on.
Don't get stuck and sink your time into a local maxima.
Maybe you'll find a market [of fools] willing to invest time into this exact locally optimal solution, but I predict it will be disappointingly small. The problem it solves isn't broadly substantial enough to warrant a specialized solution.
Only one way to know for sure, though ;)
Though I would be interested in tooling that allows clients to simply create issues by clicking an element and then saving full context (dom, screenshot, url, form state, browser and session) with that issue. Something important is too often missing from a bug report.
But then the problem is getting the client to actually use that tool.
The key thing your post is missing is that the word you're looking for is "annotations".
https://hn.algolia.com/?q=annotations https://news.ycombinator.com/item?id=22876408
Going back to some of these old posts makes me highly nostalgic for a specific era of the web when we had no reason to expect that we wouldn't always be using bookmarklets to get shit done, Facebook Open Graph was a Thing and there was an assumption that everything would soon be connected like modules using Yahoo Pipes. https://web.archive.org/web/20120320063943/http://nimblecode... https://web.archive.org/web/20120211054910/http://www.readwr...
(not affiliated - just a fan)
I think https://jam.dev/ should do it! (not affiliated - just a fan)