adhit-r / adhit-r/holocron

Mobile parity audit — every state touch-reachable

オープン
#18 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
area: a11y area: ux good first issue
主要言語
TypeScript
スター
0
フォーク
1
PR マージ指標
30日以内にマージされた PR はありません

説明

> **Skills:** TypeScript · mobile testing · DevTools debugging · responsive CSS
> **Time:** ~8 hours
> **Good for:** QA-minded engineers · mobile-first devs · iPad / phone Star Wars readers
> **Difficulty:** Beginner-friendly to Intermediate

---

## Context

The desktop layout has been the development focus. The mobile layout exists
(`md:hidden` branch in `AppShell`, `DatapadDrawer` for the bottom sheet) but
hasn't been systematically validated.

## Goal

Test every interactive state at 375px width. Document failures. Fix.

## Where to start

States to verify:
- Galaxy view: orbit + zoom on touch, planet click, Atlas toggle, plot-route mode
- Timeline view: scrubber drag on touch, era marker visibility, faction
territory legibility
- Lineage view: 3D force-graph touch handling
- Datapad drawer: peek/expand, scroll inside, Crawl button, pivot buttons
- Search palette: keyboard alternatives via mobile UI
- Holo-stage: full-bleed on mobile (no clipped overlays)
- Opening crawl: skip controls reachable

Test at 375px (iPhone SE), 414px (iPhone Pro Max), 768px (iPad portrait).

## Acceptance criteria

- A list of issues found, with severity (P0 = blocking, P1 = degraded, P2 = nit)
- All P0s fixed
- A "mobile checklist" doc added under `docs/`
- No new horizontal scrollbars on the chrome (canvas can pan)

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

Start in the AppShell `md:hidden` branch and `DatapadDrawer`, then exercise every listed state at 375px, 414px, and 768px using touch and DevTools. Record P0/P1/P2 failures, fix all P0 issues, add the mobile checklist under `docs/`, and verify that chrome has no new horizontal scrollbar while canvas panning remains allowed.

索引モデルが issue の本文から書いたものです。

評価

技術スタック
nextjs, react, tailwindcss, threejs, typescript
領域
accessibility, frontend, mobile, testing
issue の種類
バグ
難易度
4/5
見積もり時間
1〜2日
活発さ
静か
明瞭さ
おおむね明確
初心者へのやさしさ
52/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。