How Google takes feedback
google.com
google.com
http://stackoverflow.com/questions/4912092/using-html5-canva...
tl;dr JavaScript can read the DOM and render a fairly accurate representation of that using canvas
How it works:
1. You create a widget and add two lines of code to your site. 2. Visitors click the feedback button and can select highlight any part of the page to comment on. 3. Usabilla creates a screenshot (server-side) and shows feedback in a simple dashboard.
Disclaimer: I'm founder of Usabilla.
It uses html2canvas to generate site screenshot on client side.
I have to imagine that Google has a pretty automated process to understand the feedback - i'd rather see that. That's the problem I've always had with applications with millions of users.
Everyone looks at it. That doesn't solve any problem.
And my only problem with Google only appears when I'm not logged in. The irony.
The specific functionality they took away is devastating to regular users like me. When searching, results would show if a book was already in your library. You could also add it to a shelf from the search result itself. Now the search results lack that info and you must click on each result to see if it's one you already saw. This is sheer hell for discovering books that weren't there between searches.
[edit for URL fix]
The difference is subtle, but important.
Feedback: "I would use your product more if it did x."
Complaining: "Your product sucks because it doesn't do x."
In short: you're absolutely correct. Making it easier to complain doesn't help. Making it easier to give feedback does help.
Doing it within the app also gives you a lot more detail (who the user is, where they were accessing, what browser they were using, their OS, any client side exceptions, their exact actions, etc etc) without needing to rely on the user to provide it.