Play puzzles on a phone
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- accessibility, frontend
Research direction
Start with the sudoku fence in docs/puzzles.md on a phone and compare its touch behavior with tracks, which was checked through in #237. Work spans touch input, hints, key-list access, and board sizing across all five puzzle kinds; the issue says completion means each can be played from start to finish on a real phone, including entering and clearing numbers and adding pencil marks in sudoku.
Written by the indexing model from the issue text.
Description
Most of the puzzles were built for a keyboard, so on a phone some can't be played, and the hints don't apply.
To repeat it, open a document with a sudoku fence on a phone, such as the samples in docs/puzzles.md, and try to fill in a square.
What happens:
- Sudoku can't be played at all: tapping a square brings up no keyboard or number pad, and it only listens for keys.
- Every kind says "? for keys", and
?itself needs a keyboard. "Keys" doesn't mean much on a phone either.
What should happen:
- A sudoku has a way to enter a number by touch, such as a number pad, including pencil marks and clearing a square. It needs a design: where a pad goes on a small screen, without covering the board.
- On a touch screen, each kind's hint says how to play by touch, such as "Drag to lay track", and the list of keys opens with a tap, if a kind has anything left to say.
- Each of the five kinds (sudoku, tracks, maze, word search, coordinates) can be played from start to finish on a touch screen, checked on a real phone. So far only tracks has been played through that way: dragging off the board to finish it was fixed in #237.
Boards sized for a keyboard may also be small to tap: a 3×3 tracks board is about 165px across on a 412px-wide phone.
Came up in the review of #237, on a real phone. #20 noted the number pad first.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 26
Getting set up
- Ships a 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 jzheaux/reader
-
polish
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
polish
Difficulty 3/5 1-2 days Newbie friendliness 64/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OWASP/CheatSheetSeries#3018 ·
Maintainers usually reply within 1 day
-
Radix number block generates NaN after switching a negative or decimal number to binary, octal or hexPossibly taken @matthewalberto claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
mit-cml/appinventor-sources#4246 · 1 comment ·
Maintainers usually reply within 1 day
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
GoogleChrome/modern-web-guidance-src#3675 · 2 comments ·
Maintainers usually reply within 1 day