Baseline

Test builds

Put Baseline on the handset you referee with

Pre-release builds for pilot testers. Install them on a device you don’t mind wiping, and expect them to change often.

Open this page on the handset you’re testing on, or transfer the file across.

Android

APK · sideload

Not yet published

A direct .apk, installed by hand. Not from the Play Store, so Android will ask you to allow this one explicitly — that is expected, and the steps are below.

Build pending
Version —
Size —
Requires —
Released —
Package —
Signatures —

SHA-256 of the APK

Published here the moment a build is uploaded.

Signing certificate fingerprint

Published here the moment a build is uploaded.

—

iOS

TestFlight

Not yet published

iPhone and Apple Watch builds are distributed through TestFlight. Install Apple’s TestFlight app first, then open the invitation link — the build appears inside it.

TestFlight pending
Version —
Build —
Requires —
Released —
An APK will not install on an iPhone. It is an Android package format. iOS only accepts signed .ipa payloads delivered through TestFlight, Ad Hoc provisioning or MDM. If a site offers you an “iOS APK”, it is not what it claims to be.

Before you install

Check the file is the file we built

Sideloading bypasses the Play Store’s checks, so the checksum is the only thing standing between a tester and a swapped file. It takes ten seconds.

Windows
certutil -hashfile baseline.apk SHA256
macOS
shasum -a 256 baseline.apk
Linux
sha256sum baseline.apk
On the phone
Most file managers show a file hash under “Properties” or “Details”. Termux users can run sha256sum directly.
The output must match the SHA-256 printed on this page exactly, character for character. If it doesn’t, stop — delete the file and tell us. A mismatch means the download was corrupted, or it isn’t our build.

Android

Installing the APK

  1. Download the APK to the phone, or copy it across by cable.
  2. Check its SHA-256 against the one printed above.
  3. Open the file. Android will say installing from this source isn’t allowed yet.
  4. Choose Settings, and turn on Allow from this source for whichever app you opened it with — your browser or file manager.
  5. Go back and confirm the install.
  6. Turn that permission back off once Baseline is installed. It applies to every file that app opens, not just this one.
  7. Pair the watch app from the phone app’s Devices screen.

Play Protect

Android may warn that the app is unrecognised. That is Play Protect noting it hasn’t seen this package before, not a detection — it says the same of every pre-release build.

Use a spare handset

Pre-release builds can lose local data between versions. Don’t put a real fixture through one until we say the record format is frozen.

How to tell a real Baseline build from a fake one

Four things that are always true

01

It is served over HTTPS from our own domain

Builds are linked only from this page, over TLS. We will never send you an APK as an email attachment or a chat file, and we will never ask you to disable a security warning beyond the one install permission above.

02

The checksum is published beside the link

Every build shows its SHA-256 here before you download it. A build offered without one, anywhere, is not ours.

03

The signing fingerprint never changes

Every genuine build is signed with the same certificate. Android refuses to upgrade an app whose signature changed — so if an “update” asks you to uninstall first, treat it as hostile.

04

We never ask for credentials to install

No Google account, no Apple ID, no card details, no licence number are needed to install a test build. Anything asking for those during install is not us.

Found a build of Baseline somewhere other than this page? Please tell us rather than installing it.