Play puzzles on a phone

Open
#246 0 comments 0 reactions 0 assignees View on GitHub

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

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

behavior enhancement

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

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 jzheaux/reader

All issues in jzheaux/reader

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.