As I do more management (yuck) I find myself having to put together reams of commented screenshots all the time. My process for this is piecemeal - but this would definitely help. Thanks!
A few suggestions:
1. HTML, Google Docs, or PDF output would be faaaar more useful than Word. I'm actually surprised you used Word here. We must have very different work environments. :)
2. I feel like there are usability/UX recommendations other than Nielsen that might be more useful for some audiences. His advice is a bit mundane and abstract for my tastes. Perhaps the https://userium.com/ list could be of use for some. Having options here (which I agree stinks of bloatware) could be interesting.
1. There actually already is HTML output. My idea is that most people will likely copy/paste from HTML or a Word Doc to combine with their collaborators. From that perspective, PDF feels too 'finished'. And yeah, as someone else explained, I'm a PM on the Office Online team :)
2. This is great. I'm working on supporting different lists than just Nielsen's heuristics (including being able to create your own custom list). Unfortunately the one you linked to is quite long and might be quite lengthy to have in the sidebar. I'll think about that though.
My problem with Invision, which we used extensively about a year ago to redesign POP.co, is that it expects you to live in its own interface and interact with the Invision prototype on their own terms, inside their walled garden of sorts.
This is OK, and kind of makes sense in the app-driven world we live in, but to really fit into the kind of hectic, ten-different-tools workflow that we thrive in at the office, screenshots are the core lingua franca.
We can attach them to Pivotal tasks (or Hipchat convos, or anything else), forward them around (even via SMS!), scribble all over them, print them out and stick em on the wall for a meeting.
With Invision, we'd be crowded around a phone or screen, and unable to interact with the collaborative output in other tools. I came to dread receiving an Invision link in my email, especially because I couldn't tell which shortened URL referred to which project.
Overall, I've come to really hate tools that expect me to live inside them, rather than them living inside everything else I already use. I don't want to leave my flow.
This is incredibly good feedback, and if there is anyone here from InVision, they should be paying close attention.
There's also a larger lesson to be learned about finding the integration points that make the most sense to the application you're building. Things like email and calendars are obvious, I wonder what else should be considered from the same point of view.
You clarified for me the misgivings I've had with Invision. I've used it a few times on projects (as more of a stakeholder than core team member), and it just never seemed to live up to its promise. I think it was because there were some people who were not "all in" with it, and some of the key feedback was coming outside the app.
Rather than the sense of dread you mentioned, I just let other things take higher priority than the emails with Invision links. I thought it did work well when a designer led a small group through a prototype live.
Some companies, especially at the beginning, would put a trailing slash on their domain names when using .CO on a business card or other printed material.
Things have gotten better now, and millions of people have interacted with t.co, the Twitter shortener, Vine, etc., which means that .CO isn't quite as "underground" as it used to be.
I think ultimately the choice of TLD should be related to other branding decisions in that you consider your market first. So if you are pursuing a group that's very internet savvy, or startup savvy, they've probably heard of .CO and you can use it freely. (Likewise, you could probably use an unusual/industry name)
But if you are going after people who aren't familiar with URLs or domain names -- or maybe can't even discriminate between an email address and a domain name -- you'd be better off going with the safer option.
Hi all - I created UX Check as a side project over the past few months and I'm glad that people are finding it to be helpful! There are some awesome suggestions in this thread and I'm already working on a v2, so feel free to keep the ideas coming.
That is a very nice tool for taking screenshots. Thanks!
Your website had me thinking the tool was going to perform an automatic scan for usability issues. You could be a little clearer that the tool allows users to note usability issues.
Hey there, really love the extension! It's nice to have something like this and it's a good way to record thoughts and feedback.
Speaking of user experience, you should really use inline installation[1] for chrome extensions. It provides a really nice experience so that users don't need to leave your site. It also allows you to detect if the extension is installed so that way you can remove the install button for people who already have it.
Very nice. Something that will definitely prove useful.
Note: The highlight box seems to be slightly misaligned vertically on some sites. On one site I tested it seemed to be ignoring padding-top on the <body>.
Also, what would be really handy is the ability to download the result not as a document, but rather to integrate it with existing issue tracking software such as JIRA. I'm sure that's on your V2 plans with some monthly recurring plan.
Yikes, that's bad. Do you use any accessibility settings like changing the font size on websites? Or are you on an older version of Chrome? Thanks for sharing.
Current version of Chrome, but my Windows font settings are set to 110% (system-wide, not browser specific) to make it easier to view text when in a high resolution on a small monitor. I see this issue with various sites that assume a fixed font size which can never change.
If I manually add "font-size: 16px;" to your html,body CSS definition, everything displays properly. The discrepancy is occurring because you are using a fixed pixel height (eg: for the "ten heuristics" div its height is 500px) but letting the browser/system determine the font size.
I've been working on that topic too in the last year. I developed Capian (http://capian.co), a tool to help usability professionals make better heuristic evaluations faster.
I'm a full-stack developer and my partner is a UX designer. There's a lot of missing tools in our space. Great to see other people trying to address them!
I'm curious to know how the author managed to take a screenshot of the site? I know there were methods to actually recreate the DOM via some 3rd party library. Not sure if things have changed with HTML5 or others means of doing it.
I used a Chrome extension API. One alternative I've heard is copying the DOM over into a separate canvas element, which you can save as an image. I haven't tried that yet though.
That was the most frustrating part of the project. I used the Open XML SDK for Javascript. There isn't a whole lot of documentation so it was a lot of guess and check.
As I do more management (yuck) I find myself having to put together reams of commented screenshots all the time. My process for this is piecemeal - but this would definitely help. Thanks!
A few suggestions:
1. HTML, Google Docs, or PDF output would be faaaar more useful than Word. I'm actually surprised you used Word here. We must have very different work environments. :)
2. I feel like there are usability/UX recommendations other than Nielsen that might be more useful for some audiences. His advice is a bit mundane and abstract for my tastes. Perhaps the https://userium.com/ list could be of use for some. Having options here (which I agree stinks of bloatware) could be interesting.
Oh.. and extra points for using a .CO :)