sulthan
d1253e8a7b
PRODUCT.md records the durable constraints the UI work keeps having to rediscover: dark-first is binding (night reading), mobile is the target rather than the starting breakpoint, and updated_at ordering is a correctness rule the design must not decorate over. The two critique snapshots are the scored before/after (21/40, then 26/40) the card fixes were driven from — worth keeping as the record of which problems were already known, and which ones the fixes introduced. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
3.3 KiB
target, total_score, max_score, na_heuristics, p0_count, p1_count, timestamp, slug
| target | total_score | max_score | na_heuristics | p0_count | p1_count | timestamp | slug |
|---|---|---|---|---|---|---|---|
| backend/templates (web UI) | 21 | 40 | 0 | 2 | 2026-07-26T15-50-42Z | backend-templates-app-html |
Method: dual-agent (A: ab4734f79f4becbf2 · B: af2c412345f87a2d1)
Design Health Score
| # | Heuristic | Score | Key Issue |
|---|---|---|---|
| 1 | Visibility of System Status | 2 | No hx-indicator on any htmx mutation — favourite/save/delete swap silently |
| 2 | Match System/Real World | 3 | Icon-only actions rely on title= tooltips, which never fire on touch |
| 3 | User Control and Freedom | 2 | Favourite-toggle and chapter-save are instant, no undo |
| 4 | Consistency and Standards | 3 | Native unstyled confirm() for delete breaks from themed htmx-swap pattern |
| 5 | Error Prevention | 2 | Chapter input has no max, no reference to LatestChapter while editing |
| 6 | Recognition Rather Than Recall | 3 | Good persistent state; edit form doesn't show current latest chapter |
| 7 | Flexibility and Efficiency | 1 | No bulk actions, no shortcuts, no filter for "has new chapter" |
| 8 | Aesthetic/Minimalist Design | 3 | Lean; .meta/.actions rows lack visual grouping |
| 9 | Error Recovery | 1 | No failed-request UI state anywhere |
| 10 | Help and Documentation | 1 | Zero affordance explains the favourite/NEW-don't-reorder rule |
Total: 21/40 — Acceptable band
Design Specificity Verdict
Generic-competent. Nothing signals manga/night-reading/two-site-unification beyond the header text. site-{{.Site}} badge (the actual product differentiator) styled as a neutral pill, same weight as everything else.
Deterministic scan: CLI static-HTML detector 0 findings (exit 0). Browser/live detector found: tight-leading (line-height 1.25, real), overused-font/single-font (100% Roboto), flat-type-hierarchy advisory (~1.5:1 ratio). One text-occlusion hit was a false positive (detector's own leftover overlay text).
Priority Issues
P1 — Silent failure on every htmx mutation (no hx-indicator, no error UI). Fix: hx-indicator + htmx:responseError inline error text. P1 — NEW-chapter signal has no visual priority/filter despite poller existing for exactly this. Fix: elevate .new styling, add "Updated" quick-filter. P2 — Native confirm() on delete breaks dark theme, violates "no pure-white flash" a11y requirement. Fix: inline htmx confirm row. P2 — Chapter input has no upper bound/reference to LatestChapter. Fix: show "Latest: Ch N" inline, soft max warning. P3 — Single font, flat type scale, line-height under 1.3 floor. Fix: real typographic hierarchy.
Persona Red Flags
Casey (mobile, primary): 4 stacked chrome regions before content; touch-only tooltips never fire; silent failures invite repeat-tapping. Riley (stress): webkit-only line-clamp with no fallback; no-cover cards render blank with no placeholder; filter.js untested at scale.
Minor Observations
Continue-strip not tab-scoped. Fixed accent colors unverified for contrast against light theme. title= tooltips dead weight on touch.
Questions to Consider
- Why does the NEW-chapter signal carry less visual weight than the static site badge?
- Why is confirm() (guaranteed to break theme) still unreplaced given the explicit no-white-flash requirement?
- Does the ordering rule need an explanation, or does needing one mean the mental model fights the user?