Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Retro Labyrinth: mobile-first play and leave the desktop-only gate

Open
#2,003 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
22/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
frontend, mobile

Research direction

Start with the DesktopOnlyGate wrapper and the "Desktop only" hub badge, then the PlayCabinet props (onAutoPause, mobileOrientation, mobileLayout). The collapsed "Game mode, class & display" panel, the orientation-hint close button, palette chips, CRT toggle, difficulty chips and playfield container are the layout targets. Done when touch targets reach 44px, the collapsed panel is hidden or inert, the playfield fits at 320x568, and screenshots at 320, 375, 768 and 1440 are attached with the gates passing.

Written by the indexing model from the issue text.

Description

area:arcade game ready-for-agent

Part of #1985. Builds on the mobile kit (#1986).

Make Retro Labyrinth meet the phone bar in #1985, then remove its DesktopOnlyGate wrapper and its "Desktop only" hub badge.

Known from the kit playtest:

  • The orientation-hint close button is 22x22. The palette chips are 24px, the CRT toggle 16px and the difficulty chips 42px tall. All must be at least 44px.
  • The collapsed "Game mode, class & display" panel leaves its controls focusable over the playfield. Make it hidden or inert while collapsed.
  • At 320x568 the playfield container clips about 52px.
  • Wire onAutoPause, mobileOrientation and mobileLayout="fit" into its PlayCabinet.

Done when a fresh phone playtest scores at least 9/10 with no blocker or should-fix findings, the full gates pass, and the PR has screenshots at 320, 375, 768 and 1440.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
1h 44m
Merged PRs (30d)
689

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fderuiter/deruiter.dev

All issues in fderuiter/deruiter.dev

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.