hansdezwartandClaude Opus 5
11ec616270
"Do whatever you like with it" isn't an SPDX identifier, and without one F-Droid won't take the app at all. Same intent, now in a form a machine can read. The listing lives in fastlane/metadata/android/en-US/ so F-Droid reads it out of the repo and it stays in version control: title, a 65-character summary, a description adapted from the README that leads with the empty permission list, a changelog and four screenshots. The screenshots are generated from the same HTML the app runs, at 1170x2532. The harness freezes the render loop once the wanted frame is painted — a headless capture otherwise lands whenever the virtual clock runs out, by which time the delay bar has always finished draining, and the delay is the thing worth showing. Shot one is a 5-point match at 2-1 with the bar half spent; the others are the score sheet, the settings sheet from a pristine match (the gear is gone once a match is running, so that is the only honest way to show it), and a 1-point game with the score chrome absent. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
45 lines
2.1 KiB
Plaintext
45 lines
2.1 KiB
Plaintext
A backgammon clock for two players sharing one phone between them. Reserve time
|
|
plus a fixed number of free seconds each turn that never carry over — the
|
|
Backgammon Galaxy control. Defaults to 3:00 with a 12 second delay.
|
|
|
|
It asks for no permissions at all. There is no network access, no analytics, no
|
|
accounts, no ads, and nothing to configure before you can play. The whole clock
|
|
is a single HTML file inside the app.
|
|
|
|
<b>The delay is the point.</b> Most clocks give you the free seconds silently.
|
|
Here a bar drains under the big number while they run, and a quiet tick tells you
|
|
the moment your reserve starts moving. That is the moment worth hearing across a
|
|
board.
|
|
|
|
<b>How it works</b>
|
|
|
|
* Tap your own half to end your turn and start your opponent's clock.
|
|
* The waiting player's taps are ignored, so a stray hand can't stop the clock.
|
|
* A tap registers when you lift your finger, and only if it didn't move — so
|
|
swiping up to leave the app never costs anyone their turn.
|
|
* Your clock runs until you lift, and holding past zero flags you.
|
|
|
|
<b>Matches</b>
|
|
|
|
Set the match length to any odd number of points up to 29. The time you set is
|
|
per point, so a 5-point match at 2:00 a point puts 10:00 on each clock. Each half
|
|
of the screen reads the score from that player's own side of the board, so both
|
|
players see their own score on the top line.
|
|
|
|
At one point there is no match to keep score of, and the score lines disappear
|
|
entirely — you get a plain single-game clock with a move count.
|
|
|
|
<b>It survives being closed</b>
|
|
|
|
Settings and the match in progress are kept on the device: the score, both
|
|
clocks, the move counts, whose turn it is and how much delay was left. Force-quit
|
|
it mid-match and it all comes back. The one thing it can't restore is time that
|
|
passed while the app was closed, so it returns paused rather than charging anyone
|
|
for the gap — a crash shouldn't decide a game.
|
|
|
|
Pause freezes mid-turn and resumes exactly where it stopped, delay included.
|
|
Reset takes two taps, so one stray thumb can't wipe a live match.
|
|
|
|
Five colour schemes, three sounds generated on the fly, and the screen stays
|
|
awake while you play.
|