Tag: visual feedback

You might not consider screenshots as some form of art. Well, we do. We consider ourselves as screenshot lunatics.

We even created our very own visual bug tracking tool revolutionizing the way we report bugs and collect feedback. With screenshots. Pretty cool, huh?

In this post I’m going to show you the ins and outs on how to take a great screenshots. Whether you want to capture a mobile screenshot, or you’re managing screenshots for web projects as a designer or developer.

Just a few days ago Github announced their new update of Github Issues. You can see the updates with some screenshots from here. Also, please take a look at the new Deployment API if you haven’t already.

Move beyond the simple Issues

Starting at the same day something else were released, not by GitHub, but still connected to Issues. Let me show you, how you can use a chain of tools to make your GitHub Issues even more useful for your team.

The players:

A website

Imagine you have a website, that is hosted on Github, like this one, which is the code-base for input.mozilla.com.

A team/community

Let’s also imagine that you have a team or a community which is handling bug-requests. You have a designer and a programmer at least.

Adrian Smith is a self-employed software architecture and performance consultant currently working on a platform for HR departments that implements quite a few special features. Adrian decided to use Usersnap for this project, to gather specific feedback from his client during the development process.

“We’re using Usersnap on our dev server as the site isn’t live yet. It helps my client to point out and describe what he’d like to see improved. I like this way of receiving feedback. He can highlight areas of the screen etc., i.e. he can really visually say what’s wrong. Which is of course way better than writing an email following the storyline ‘on the third navigation point, the second area, the 3rd word is in a strange position’!”