Mobile: lessons reference the arena, but the arena pane doesn't exist on phones
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- markdown, typescript
- Domain
- documentation, frontend
Research direction
Start with useIsMobile in ui/src/App.tsx, which hides the arena pane on phones, and with the arena-referring lines in ui/public/docs/learn.md and the lesson pages. The issue leaves open whether to add a mobile arena toggle or only fix the copy, so confirm the direction with the maintainer before building the toggle. Done means a phone user following lesson 1 is never told to look at the arena, whether through a note on /learn or a working peek.
Written by the indexing model from the issue text.
Description
From the 2026-07-17 UX review.
Problem
On phone-sized viewports the arena pane is dropped entirely (ui/src/App.tsx, useIsMobile) — a defensible call — but lesson copy says things like "watch it run in the arena on the right" (ui/public/docs/learn.md, lesson pages), which is impossible there. A phone learner follows the instruction and nothing they can see happens.
Suggested fix
Either:
- Offer a peek: an arena tab/toggle on mobile (the
useArenaStreamdata stays wired up on mobile already — only the render is gated), or - Set expectations in the copy: a short note on /learn and in early lessons that the live arena needs a wider screen.
The copy fix is cheap and could land first; the toggle is the better experience. Note #131 (responsive layout) is closed — this is the remaining gap between the mobile layout and the course copy.
Acceptance
A phone user following lesson 1 is never told to look at something that isn't on their screen.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 8m
- Merged PRs (30d)
- 8
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from LeeAdcock/robocodeJs.com
-
priority: medium tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
LeeAdcock/robocodeJs.com#411 ·
Maintainers usually reply within 1 day
-
enhancement priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LeeAdcock/robocodeJs.com#254 ·
Maintainers usually reply within 1 day
-
good first issue priority: low tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LeeAdcock/robocodeJs.com#146 ·
Maintainers usually reply within 1 day
-
dependencies priority: low tech-debt
Difficulty 1/5 Under an hour Newbie friendliness 15/100
LeeAdcock/robocodeJs.com#413 ·
Maintainers usually reply within 1 day
-
priority: low tech-debt
Difficulty 3/5 Half a day Newbie friendliness 32/100
LeeAdcock/robocodeJs.com#412 ·
Maintainers usually reply within 1 day
All issues in LeeAdcock/robocodeJs.com
Similar issues
-
documentation good first issue hacktoberfest help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libredb/libredb-studio#1756 ·
Maintainers usually reply within 1 day
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 72/100
lingdojo/kana-dojo#32365 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
friction
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kentcdodds/kody#3706 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
copperheadhq/copperhead#378 ·
Maintainers usually reply within 1 day