Tracker: mobile and small-screen support
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, react
- Domain
- frontend
Research direction
This tracker splits the work into #299 (navigation), #300 (workflow layout), and #301 (visualizations). Start with the relevant sub-issue; the mentioned entry points include pages/index.js, pages/_app.js, pages/browse/index.js, and the five pageblock components. Check each sub-issue for its specific acceptance criteria; done means Redux_GUI works in a phone browser across the scoped areas.
Written by the indexing model from the issue text.
Description
Umbrella for making Redux_GUI usable on phones and other small screens.
Scoped against ReduxAPI_GUI on 2026-09-22. Redux_GUI and Redux_Frontend are being treated as separate alternatives, so this tracker covers Redux_GUI only; the equivalent work for the other frontend is tracked in its own repository.
Starting position
Better than it first appears. The viewport meta tag is present (pages/_app.js:24), the workflow page is already a vertical stack rather than a desktop grid, every SVG visualization already uses viewBox so nothing overflows its container, pages/browse/index.js is genuinely responsive already (xs:12 md:3 sidebar, xs:12 sm:6 md:4 cards), and drag-and-drop already registers a TouchSensor.
So this is not a rewrite. It is one missing component, one unstyled area, and one design question.
Sub-issues
- #299 — navigation disappears below 900px. Highest impact, smallest fix. Four of five pages are unreachable on a phone today.
- #300 — core workflow page has no responsive layout. Zero breakpoints across
pages/index.jsand all five pageblock components. - #301 — visualizations scale but are illegible at phone width. The largest and least certain piece.
Suggested order is #299, then #300, then #301. #299 stands alone and is worth doing whether or not the rest is scheduled.
Out of scope
Print layouts, offline support, and native apps. This is about the existing site working in a phone browser.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 18
- Avg merge
- 23h 39m
- Merged PRs (30d)
- 39
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No 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 ReduxISU/Redux_GUI
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
All issues in ReduxISU/Redux_GUI
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
lyswhut/lx-music-desktop#3026 ·
-
good first issue server
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
openstreetmap/iD#13054 ·
Maintainers usually reply within 1 day
-
community marketing priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
TMHSDigital/Free-Game-Dev-Assets#151 ·
Maintainers usually reply within 1 day
-
Read a vector index's quantization back on Neo4j 2026.10, which reports vector.quantization.typeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
liberation-data/drivine#231 ·
Maintainers usually reply within 1 day