Skip to content

PRODUCT.md

Latest commit

 

History

History
37 lines (23 loc) · 2.45 KB

PRODUCT.md

File metadata and controls

37 lines (23 loc) · 2.45 KB
Raw

Product

Register

product

Users

BenchSift serves developers, technical decision-makers, and AI practitioners who need to narrow a large model catalogue and make an evidence-based choice. They scan rankings quickly, filter by capability or provider, then compare a small shortlist in depth across desktop and mobile contexts.

Product Purpose

BenchSift brings real model benchmarks, speed, latency, pricing, context, modality, availability, and provider data into one dependable decision surface. Success means a user can find relevant models, understand trade-offs, and share or revisit an exact comparison without fighting the interface or doubting the data.

Brand Personality

Precise, restrained, pragmatic. The product should feel like a trustworthy technical instrument: calm enough for dense reading, direct in its language, and responsive at every interaction.

Anti-references

  • A wholesale visual redesign that replaces BenchSift's existing warm-neutral, monochrome identity.
  • Generic AI SaaS marketing aesthetics, decorative gradients, neon accents, or gratuitous glass effects.
  • Fake, seeded, or hard-coded operational data that makes the catalogue look more complete than it is.
  • Decorative motion or delayed navigation that makes the product feel slower than the underlying action.
  • Desktop-only density that hides core comparison actions behind hover or produces cramped mobile layouts.

Design Principles

  1. Evidence before decoration. Make real metrics, provenance, and data gaps easy to understand.
  2. The URL is a durable state. Filters and comparisons that users may revisit or share must navigate predictably and preserve their exact selection.
  3. Dense, then progressively disclosed. Desktop can show breadth; smaller viewports keep the same information architecture while revealing detail in focused layers.
  4. Immediate interaction feedback. Selection, navigation, loading, and removal states must respond within a human-perceptible instant.
  5. One visual language. Reuse the existing semantic tokens, restrained surfaces, Geist typography, and familiar controls across every route and theme.

Accessibility & Inclusion

Target WCAG 2.2 AA. All core workflows must be keyboard-operable, retain visible focus, meet contrast requirements, expose clear names and states to assistive technology, provide at least 44-by-44-pixel touch targets on coarse pointers, and respect reduced-motion preferences without removing functionality.