docs: Android is on Google Play production, not a closed test track #40

2026-08-04T17:49:25Z

enricobuehler commented

2026-08-04 17:49:25 +00:00

Follow-up to punktfunk-website#2, which pointed the website's Android download card at the live Play listing. downloads.ts there names these docs as the source of truth, so they needed the same pass.

Play production access landed 2026-08-01 and the listing is live, but the docs still told Android users to request a tester invite on Discord — and warned that the Play link "only resolves once your account is on the tester list". Both are now wrong, and the install page is the first thing a new Android user reads.

The distinction the docs were collapsing

Stable is a public Play listing, no invite. Canary is unchanged — still the invite-only Internal testing track. The old text described both as "test tracks", so every page now draws that line explicitly rather than dropping the canary invite path entirely.

Files

File	What was stale
`install-client.md`	The whole Android section led with "request a tester invite"; the device table called it "Beta — a Play test track". Rewritten to lead with the store link, with the canary invite moved to its own note at the end.
`clients.md`	"on Google Play as a test track (closed testing for stable…)"
`channels.md`	Subscribe table said stable = "Play closed (alpha) track"; plus the release-process fix below.
`support-matrix.md`	"Distributed on Play's closed (alpha) track for releases"
`uninstall.md`	Told people to ask on Discord to be taken off a tester list that no longer gates the app.

Release-process correction

channels.md also claimed CI "uploads stable to testing tracks only — it never auto-publishes to the public stores", and that someone promotes alpha → production by hand in the Console. Since 43e3c7b6 that is not how it works: android.yml:176 resolves TRACK="production" on refs/tags/v* and uploads with --status completed, so a tag ships to 100% with no further click. Apple is still manual, so that half stands and is kept.

I verified this against the workflow in-tree rather than from the changelog.

Verification

docs-site/ does not build standalone in this checkout (src/components/Footer.tsx and src/routes/api/index.tsx import packages that aren't installed locally — CI builds it against the workspace), so this is checked by inspection:

The ## Android heading is unchanged, so the #android anchor still resolves — it's linked from install-client.md's own device table, from clients.md, and from the website's DOWNLOADS.docsInstallClientAndroid fallback.
Code fences in install-client.md balance (16 fence lines).
All three edited markdown tables have uniform column counts.
The Play listing itself returns HTTP 200 — worth stating, since it 404'd for the whole review window.
Re-grepped for invite / closed test / alpha track / tester list: every remaining hit is an intentional canary-track line.

Follow-up to [punktfunk-website#2](https://git.unom.io/unom/punktfunk-website/pulls/2), which pointed the website's Android download card at the live Play listing. `downloads.ts` there names these docs as the source of truth, so they needed the same pass. Play production access landed 2026-08-01 and the listing is live, but the docs still told Android users to request a tester invite on Discord — and warned that the Play link _"only resolves once your account is on the tester list"_. Both are now wrong, and the install page is the first thing a new Android user reads. ## The distinction the docs were collapsing **Stable** is a public Play listing, no invite. **Canary** is unchanged — still the invite-only **Internal testing** track. The old text described both as "test tracks", so every page now draws that line explicitly rather than dropping the canary invite path entirely. ## Files | File | What was stale | |---|---| | `install-client.md` | The whole Android section led with "request a tester invite"; the device table called it "Beta — a Play test track". Rewritten to lead with the store link, with the canary invite moved to its own note at the end. | | `clients.md` | "on Google Play as a **test track** (closed testing for stable…)" | | `channels.md` | Subscribe table said stable = "Play **closed (alpha)** track"; plus the release-process fix below. | | `support-matrix.md` | "Distributed on Play's **closed (alpha)** track for releases" | | `uninstall.md` | Told people to ask on Discord to be taken off a tester list that no longer gates the app. | ## Release-process correction `channels.md` also claimed CI *"uploads stable to testing tracks only — it never auto-publishes to the public stores"*, and that someone promotes alpha → production by hand in the Console. Since `43e3c7b6` that is not how it works: `android.yml:176` resolves `TRACK="production"` on `refs/tags/v*` and uploads with `--status completed`, so a tag ships to 100% with no further click. Apple is still manual, so that half stands and is kept. I verified this against the workflow in-tree rather than from the changelog. ## Verification `docs-site/` does not build standalone in this checkout (`src/components/Footer.tsx` and `src/routes/api/index.tsx` import packages that aren't installed locally — CI builds it against the workspace), so this is checked by inspection: - The `## Android` heading is unchanged, so the `#android` anchor still resolves — it's linked from `install-client.md`'s own device table, from `clients.md`, and from the website's `DOWNLOADS.docsInstallClientAndroid` fallback. - Code fences in `install-client.md` balance (16 fence lines). - All three edited markdown tables have uniform column counts. - The Play listing itself returns HTTP 200 — worth stating, since it 404'd for the whole review window. - Re-grepped for `invite` / `closed test` / `alpha track` / `tester list`: every remaining hit is an intentional canary-track line.

enricobuehler added 1 commit 2026-08-04 17:49:29 +00:00

docs: Android is on Google Play production, not a closed test track

ci / rust-arm64 (pull_request) Successful in 1m29s

Details

ci / web (pull_request) Successful in 1m2s

Details

ci / docs-site (pull_request) Successful in 1m12s

Details

ci / rust (pull_request) Successful in 6m48s

Details

e629606e39

Play production access landed 2026-08-01 and the listing is live, but the
docs still told Android users to beg for a tester invite on Discord and
warned that the Play link "only resolves once your account is on the
tester list". Both are now wrong, and the install page is the first thing
a new Android user reads.

Stable is a public Play listing. Canary is unchanged — it still goes to
the invite-only Internal testing track — so each page now draws that line
explicitly instead of describing both as test tracks.

Also corrects the release process: channels.md said CI "never
auto-publishes to the public stores" and that someone promotes alpha ->
production by hand. Since 43e3c7b6 a vX.Y.Z tag publishes to production
at 100% with no further click (android.yml resolves TRACK=production on
refs/tags/v*). Apple is still manual, so that half stands.

Touches install-client.md, clients.md, channels.md, support-matrix.md and
uninstall.md — the last one told people to ask on Discord to be removed
from a tester list that no longer gates the app.

enricobuehler merged commit 91aa684f0d into main

2026-08-04 17:53:29 +00:00

enricobuehler deleted branch worktree-docs-play-production

2026-08-04 17:53:40 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: unom/punktfunk#40