Public Lab Research note


Findings from UI Analysis of PL website

by sylvan | March 04, 2019 20:10 | 90 views | 1 comments | #18467 | 90 views | 1 comments | #18467 04 Mar 20:10

Read more: publiclab.org/n/18467


I've been conducting an analysis of the Public Lab website's UI. In this analysis I've included Ann's UI interviews, Eva's redesigns, mockups of potential changes to the website, people's GitHub conversations, and my own heuristic review. (Here's a nice page describing what heuristic review is.) The analysis is guided by two key main website goals: 1) demonstrate what Public Lab is and what it does and 2) demonstrate what a given user can do with Public Lab.

High-level of summary of what I've found so far

  • New users don't know understand what Public Lab is and does.
  • Existing users can't find what they need.
  • Homepage

    • does not provide enough information to engage different audiences: newbie, repeat users who wants to learn more about projects, etc, repeat user who wants to contribute, searching for kits, searching for tools. Experts users are better off.
  • Dashboard is not actionable enough. Its purpose and use should be better defined. (Eva has done some nice work on it here.)

    • Need to be rethought and re-prioritized. Consider engage the community in a way similar to what we plan to do with the Homepage.
  • Search needs to be improved. Who does it serve? If it only helps the most experienced users currently, consider removing it from the navigation bar until it works better.
  • Tools are hard to find and are something people are interested in. They should be highlighted more, especially, MapKnitter, Spectral Workbench, and Infragram.
  • Similarly some people really want kits but they are hard to find and, once found, hard to navigate through. What about a layout like this?

Recommendations to Address Concerns

Overall, work towards simplicity and clarity. More specifically:

  • Users need a clearer layout of information over all and less unnecessary (or lower priority) information.
    • Define purpose for each section and page and only include what is necessary for it.
    • Define a set of page layouts and their users. Then modify pages to follow layouts.
    • If it doubt, leave it out. If you can't, put it on a separate page in the section and then link to it.
    • Imagine you are new to the page. What are you looking for, where does your eye go (does your eye know where to go?, and can you find what you need?
  • Create a Style Guide and engage the community to contribute to its design and then to use it. Could start with content page type. Also collection page type later.

A Style Guide could include

  • Redesign front page
  • Redesign dashboard page.
  • Page types by content and with examples, similar to this or to this.
  • It should define the style of all elements (typography, icons, color) but even more important, should suggest how to incorporate the elements through description and examples.

Request for Help

My next step is to sort and categorize the issues I've found and create actionable GitHub issues based on them. Before I do that, I wanted to share what I've been working on and see if anyone has any feedback on it. Does this feel right to you? What does or doesn't? If you are someone who picks up issues on GitHub, what can I do to make them most actionable for you?


1 Comments

This is really great, thanks @sylvan!!! Lots to build on here.

I think there may be two paths forward here - first, I'd love to see the draft list of issues and we can probably help refine/build out that list a bit even before it's ready to be turned into GitHub issues.

Second, the STYLE GUIDE!!! This is going to be great and I'm eager to get started on it. Thanks!!!

Reply to this comment...


Login to comment.

Public Lab is open for anyone and will always be free. By signing up you'll join a diverse group of community researchers and tap into a lot of grassroots expertise.

Sign up