Skip to content

Historical view redesign #273

@adibarra

Description

@adibarra

Feedback and analytics suggest the current historical view is hard to use. Many users select a GPU to compare but then struggle with the date range and intermediate-date selection, and the date-selection shortcut buttons are largely ignored. Come up with a design for a better implementation.

The priority audience is technical users who use the site frequently and want to move fast through repeated comparisons, without alienating first-time visitors who don't yet know the data model.

Requirements

  • A fast, low-friction flow for repeat users. Picking a GPU or GPUs and exploring their history over time should take few clicks, with sensible defaults and keyboard-friendly affordances where it helps.
  • Approachable enough that a first-time visitor can pick a GPU and land on a meaningful curve-over-time view without having to fully understand the date model up front.
  • Date range and intermediate-date selection should feel obvious; the existing shortcut buttons should either be redesigned to actually get used or replaced with something better.
  • Whatever shape the new selection takes, it must roundtrip through the URL so shared links reproduce the exact view.
  • Consider splitting into a latest data view tab and historical data view tab?
  • Analytics events on the new selection affordances so we can measure whether the redesign actually moved usage.

Deliverable

A design (mocks, prototype, wireframes, or annotated walkthrough) plus a short writeup of the thinking: what's wrong with the current flow, what you changed, and why. This one is fully up to you but ideally users familiar with the current layout should not struggle too hard with the updated layout.

Metadata

Metadata

Assignees

No one assigned

    Labels

    diff/hardRequires in-depth knowledge of codebasep1Fix soon, high priority

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions