Mobile app release notes

Per-version notes for the DisplaySync mobile app on iOS and Android.

How to read entries

Each release entry calls out:

Field	What it tells you
iOS version	The version pushed to TestFlight for this release
Android version	The version pushed to Google Play internal testing for this release
Highlights	New features and notable improvements
Bug fixes	Targeted fixes
Backend compatibility	If this release requires a specific minimum backend version (rare; called out only when relevant)

iOS and Android versions usually move together. When they diverge — for platform-specific fixes — the version numbers are called out separately.

Versioning

Semantic versioning, same convention as the rest of DisplaySync:

Major — incompatible workflow changes; rare
Minor — new features, backward-compatible
Patch — bug fixes

How updates reach you

The mobile app is distributed through:

iOS: TestFlight — testers receive an invite link and install via the TestFlight app.
Android: Google Play internal testing — testers join the internal-testing track via an opt-in link and install through Google Play.

Once enrolled, both platforms surface new builds in their respective tester apps; users tap to install when ready.

The mobile app talks to the same backend as the dashboard. Backend deploys are wire-compatible across mobile minor releases — meaning a user on an older mobile app version can still claim signs and view fleet status.

If a particular release does require a minimum backend version, that's called out explicitly in the release entry.

Older versions

We don't force-upgrade old versions out of the field. A tester on an older build can keep using it until TestFlight or Google Play internal testing removes it for compatibility reasons.

Releases

Per-version release notes will be published here as they ship. For now:

Latest available: check the TestFlight app (iOS) or the Google Play internal-testing track (Android) for the current build.
Historical versions: App Store Connect and Google Play Console have full build histories internally.

If you're seeing a behavior that doesn't match expectations and you suspect a mobile-side bug, include the iOS or Android app version in your support request — find it in Profile → About within the app.