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.
but what if client had a crappy old browser but you rendered with modern browser, which will be rendered differently. Wouldn't be better if feedback contained computed HTML doms and you could render yourself with a given client?
The really crappy old browsers won't see the feedback button. We do store and show HTML doms, which helps to debug if necessary, but most of our users collect feedback on such a large scale that it would be too time consuming to offer a manual solution like this.
Great actionable insights. A good heads up to have another critical look at our own messaging schedule. I especially like the message anatomy examples. Timing messages on specific event triggers, instead of just session counts would even make more sense.