versionCode 2. The one user-visible change since 1.0 is the navigation bar
staying on screen; public_html/ is untouched, so the service worker cache
keeps its name and no web user sees a different page.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Hans's edit. The long description is a feature list now rather than prose,
and both mention the scorekeeping, which the old text left out.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
All four listing shots were captured before the sheet-shadow fix, so each
carried the dark band along the bottom. Regenerated against the fixed
build; every one now measures a flat bottom band. The score sheet shot is
byte-identical and unchanged — an open sheet covers the bottom of the
screen, so the closed sheet's shadow was never visible in it.
Adds a fifth shot of the timeout, the most distinctive thing the app does
and the one state that had no picture.
Hans's description credits the design and the Chess.com inspiration.
Checked against F-Droid's documented limits: title 16/50, summary 66/80,
description 1644/4000, changelog 180/500, and <b> is the only markup, on
their allowed list.
.gitignore picks up *.swp and *~ so an editor swap file can't be
committed by accident.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Tightens the summary and cuts the description back: the Backgammon
Galaxy reference and the "How it works" list are gone, leaving the one
line about tapping your own half. His wording, his call on what a listing
needs to say.
Line endings checked across all four files: LF throughout, no CRLF, no
BOM, trailing newline on each. Summary is 66 of the 80 characters
allowed, description 1552 of 4000.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
"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>
hansdezwartandClaude Opus 5