What Do You Look For In Screenshots?

_iris asks: "Most software creators offer screenshots of their software in action. Screenshots are also included in most 3rd party software reviews and previews. The screenshots are usually focused on the unique features of the program. When I am evaluating software, I am usually interested in how the software differs in the more mundane ways. I'm more interested in differences in the file open/save dialogs, what program presents to me when I first open it, how the help system is integrated into the system, etc. My reasoning is that if there is only one or two programs that accomplish my needs, it doesn't matter much how it works or what it looks like because I am stuck either using it or writing my own. Do you care about the unique features or do you care about the slight differences in the common features or do you focus on something else entirely?"

Comments

Save Me!

[fm6]

I'm more interested in differences in the file open/save dialogs, what program presents to me when I first open it, how the help system is integrated into the system, etc.

Which should all be as boring and predictable as possible, so that users can leverage their experience with other applications. Unfortunately, everybody seems to use these features to exercise their creativity, especially in multimedia apps.

Lots

[mboverload]

When it comes to software, screenshots are one of the best tools to get an idea of the software's quality before you even download it.

Poor interfaces (esp if they do not follow the windows theme or use stupid eye candy) are a complete turn off to me and usually a GOOD indicator of the program's end value. I want LOTS of screenshots showing me each of the features. Perhaps a few screenshots in the actual review, and a link to a gallery with thumbnails of each of the shots and a link to a full resolution version.

At least for me, I like to see the whole screen in at least one of the shots. I'm not sure why, but it seems to convey some kind of honesty to me.

See the MythTV site to see a good idea of how screenshots can help someone evaluate a product

Unique and Salient Features

[twitter]

Submitter says:

I'm more interested in differences in the file open/save dialogs, what program presents to me when I first open it, how the help system is integrated into the system, etc. My reasoning is that if there is only one or two programs that accomplish my needs, it doesn't matter much how it works or what it looks like because I am stuck either using it or writing my own.

So, if how a program works is not what you look for in a review, what are you looking for? Is it still April Fools in here? Now for a straight answer, because the subject is actually worth talking about.

Divide and conquer. Everything has it's place and it's better to reference non core items. Know your focus and stick to it and you won't waste the reader's time.

The submitter throws out a number of examples. Open/save dialogs are unique features of meta projects like Gnome and KDE. I'm very interested in how those work when I'm looking at a new window or file manager. KDE sockets have support for samba, sftp, ftp, http, audiocd and more, how cool is that? Screen shots of those are impressive and can be found at KDE's site. When reviewing a media player, lyric fetching, cover management or list generation are how the program works and what's important. It's nice to know that the media player works with the system's underlying file manager and you can get your files by sftp, but you can just say so and link back to the KDE screenshots. The same can be said about skins, which may add character or distract depending on what program you are talking about.

I teach a Linux Class to newbies, so this is something I have to consider often. I only want to teach the important parts of each program and have to be careful about the screenshots used for step by step instruction. Attention spans are limited, so I have to be picky and well organized while I try to cram as much as I can into each class. When teaching, I have to ask myself how I use the program and what I like about it. I'll often show only a region of a program so that it stands out. The result is a very select series of images which show off the strengths of the program. People are not interested in weaknesses. If a program has a weakness in a peripheral function, no one cares. If the weakness is in core function, I won't be teaching with it.