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.
I find it annoying how you have to restart the tool for each individual element. Especially as you have to go through the How Does It Work screen every time. I think skipping the How Does It Work screen on subsequent pieces of feedback would be better.
I wish Google would share the process post submission and how they analyze and respond to feedback. I find a process like this to capture feedback over <or disproportionately> solving the easy part of a feedback loop.
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.
What good is Feedback when Google is determined to take away features from something like Google Books? You can complain all you want but they won't revert. Just making it easier to complain does nothing to fix anything.
This feedback webapp had been available to Google+ users since Google+ initially launched as invite only to the public. It used to be at the bottom right of the page.
Was it for all pages or just G+ pages? The only time I saw it before was after a Youtube UI update (long before G+), and I was sad I couldn't use it elsewhere on their site... Definitely glad that it's been rolled out to more parts of their site now.
An astoundingly high percentage of people would be unable to snap a screenshot and attach it. Let alone highlight the issue and black out anything sensitive.
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.
It might be easier for you, and for lots of other HN readers too, but what about all the other people in the world? People who when they hear the word "code" think vertically scrolling green letters on the screen.
You missed the "edit screenshot in photo editor to highlight and black out info" part. Having used this internally, I can say yes, this tool flows very well. I don't know if we do this, but you could imagine clustering feedback by the highlight pattern to automatically gauge the frequency of similiar complaints.
[+] [-] jonknee|13 years ago|reply
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
[+] [-] SunboX|13 years ago|reply
https://github.com/niklasvh/html2canvas
[+] [-] pveugen|13 years ago|reply
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.
[+] [-] jonnymkramer|13 years ago|reply
[+] [-] richardkeller|13 years ago|reply
[+] [-] premist|13 years ago|reply
It uses html2canvas to generate site screenshot on client side.
[+] [-] dawernik|13 years ago|reply
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.
[+] [-] huge_asshole|13 years ago|reply
[+] [-] naww|13 years ago|reply
And my only problem with Google only appears when I'm not logged in. The irony.
[+] [-] eavc|13 years ago|reply
[+] [-] mikecane|13 years ago|reply
[+] [-] j_baker|13 years ago|reply
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.
[+] [-] aristus|13 years ago|reply
[+] [-] ditzy|13 years ago|reply
[+] [-] jcollins1991|13 years ago|reply
[+] [-] theone|13 years ago|reply
[+] [-] ams6110|13 years ago|reply
[+] [-] jonknee|13 years ago|reply
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.
[+] [-] lmirosevic|13 years ago|reply
[+] [-] robrenaud|13 years ago|reply
[+] [-] zaphar|13 years ago|reply
[+] [-] adgar|13 years ago|reply
[deleted]
[+] [-] joshka|13 years ago|reply
[+] [-] meeech|13 years ago|reply
[+] [-] zhuzhuor|13 years ago|reply
[+] [-] MaysonL|13 years ago|reply