I was just entering an expense on Splitwise and I noticed a subtle little widget in the bottom of the screen saying “Feedback”. “Aha!” thinks me. “This is exactly the sort of thing all websites should do”. So I click it and find out it’s made by Uservoice.
Websites need user-feedback. They need it all the time. So we need to be constantly offering users the opportunity to tell us what they think, but also not annoy users by bugging them all the time, and somehow try to avoid getting 50 of the same issue being submitted.
Well done Uservoice
I think Uservoice got this exactly right. You get a subtle link appear on the side of the site saying one word - “feedback”. You probably noticed it, instantly know what it is there for, and it’s easy to ignore if you want.
When you click it, you get given a list of current suggestions on the left that you can vote on, or you can submit your own suggestion on the right. It’s perfect.
I use the service on this very site (look to the right). Please click it to see Uservoice in action and please leave me some feedback :).
The missing link - Github Issues integration
Immediately I thought “where will these suggestions be stored?” because I was already managing my own list of ideas in Github Issues (augmented with Huboard) and I didn’t like the idea of having to maintain two lists, or manually copy issues between the two.
Someone had already suggested integration to Uservoice, but it turns out there’s already a slick solution with Zapier.
Zapier is an integration service - for linking various different APIs. And they already have built-in support for linking Uservoice to Github Issues.
But how much does it cost?
For this website I certainly can’t afford to pay for either service. So it’s a good thing that both Zapier and Uservoice follow a similar model to other modern digital projects like Heroku. That is - it’s free for light or personal use, but when you want to scale it you have to start paying.
Which suits me just fine.