Historical view redesign / 历史数据视图重新设计

Open
#273 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
analytics, design, frontend

Research direction

Start by reviewing the current historical data view, including GPU comparison, date-range and intermediate-date selection, shortcut buttons, URL state, and existing analytics behavior. Produce mocks, a prototype, wireframes, or an annotated walkthrough plus a short rationale; done means the proposal addresses repeat and first-time users, reproduces the exact view through shared URLs, and measures the new selection affordances.

Written by the indexing model from the issue text.

Description

diff/hard p1

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.

中文说明

用户反馈和数据分析表明当前的历史数据视图不够好用。许多用户选择 GPU 进行比较后，在日期范围和中间日期选择上遇到困难，日期快捷按钮几乎无人使用。需要重新设计该功能。

目标受众优先考虑频繁使用网站的技术用户，同时不疏远初次访问者。要求包括：低摩擦的操作流程、直观的日期选择、URL 状态保持（以支持分享链接）、以及埋点分析事件以衡量改版效果。

交付物为设计方案（原型/线框图/标注说明）及简要设计思路说明。

Dominant language
TypeScript
Stars
46
Forks
19
Avg merge
9h 52m
Merged PRs (30d)
332

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SemiAnalysisAI/InferenceX-app

All issues in SemiAnalysisAI/InferenceX-app

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.