Kidoko Learning

Downloads

How the software reaches devices — what is available today and what still requires a human-held store account or public hosting. There is no public app-store listing yet.

Today: pilot devices are provisioned by the programme with signed builds — nothing on this page is a self-serve public download. Store listings are prepared, not submitted.

Signed Android build — programme-provisioned

available For: pilot school tablets

Pilot devices receive a signed Kidoko build installed by the programme (sideloaded APK or provisioned device image). This is the supported channel today: it needs no app-store account and works on tablets that stay offline.

Google Play

requires store account For: public Android users (future)

The Play Console listing is prepared — truthful declarations, screenshots and reviewer notes exist in the release pack — but nothing is submitted.

What is missing: requires: store account — a human-held Google Play developer organisation account.

Apple App Store / TestFlight

requires store account For: public iPhone and iPad users (future)

Same posture as Google Play: prepared, not submitted.

What is missing: requires: store account — a human-held Apple Developer account.

Learner web app (PWA)

planned For: learners on shared or family devices (future)

The offline-capable learner PWA runs on staging surfaces during development; a public URL is part of the hosting cutover.

What is missing: requires: public hosting — production DNS/hosting for the PWA.

School hub software

available For: school operators

The local school hub — a small server that caches content and relays sync on the school LAN — is deployed by an operator during site onboarding, not self-serve downloaded.

Content packs

planned For: provisioned devices

Lessons and media travel as signed content packs verified on the device. Packs ship inside the programme's provisioning flow; nothing is released to the public catalog yet.

What is missing: requires: content release — no course has passed the release gate.

Verifying a build

Release builds are signed; the certificate fingerprint is recorded in docs/release/store-submission/signing-certificate.md in the engineering repository, and the distribution runbook (docs/ops/beta-distribution.md) shows the verify step. Ask the programme team for the fingerprint before trusting a build — see help and contact.

Statuses above come from content/downloads.json on https://kidoko.app — a channel only renders “available” when it cites a real artifact.