Releases
TREX OTT App Release Management
Shipping a new build of a branded app without breaking the installs your customers already have.
Before you distribute anything
- Test on a TV, not only a phone
Remote navigation, focus order, icon rendering and text truncation all differ on a TV launcher. Most release problems in this category are TV-only.
- Check the upgrade path, not just a clean install
Install the previous build, sign in, then install the new one over it. Confirm the customer is still signed in afterwards. A build that silently logs everyone out generates a support wave.
- Record the version and the checksum
Keep the version name, version code, file size and SHA-256 of every build you distribute. When a customer reports something odd, the first question is which build they are on.
- Keep the previous build available
If the new one has a problem on some device family, you want somewhere to send people while it is fixed.
Version numbers
Android uses two: a human-readable version name and an integer version code. The version code must increase on every build or Android refuses to install it over the existing app — and the error message the customer sees does not explain that. If an update “will not install” for everybody, this is the first thing to check.
Never reissue a changed APK under a version code that has already been distributed. Two different files claiming to be the same build is unsupportable, because you can no longer tell what a customer is running.
Distributing it
| Route | Works for | Watch out for |
|---|---|---|
| Direct APK link | Phones, tablets, Android boxes with a browser | Customers must allow installs from that source once |
| Downloader code | Firestick, Fire TV, Android TV | Codes point at a URL — update the target, keep the code stable |
| In-app update prompt | Builds that support it | Test the prompt itself; a broken updater strands everyone |
| Your own developer account on a store | Phones | Policy in this category is restrictive; do not depend on it |
Telling customers
Say what changed in plain language and whether they need to sign in again. If the answer is yes, send their credentials with the announcement rather than waiting for the messages.
Questions
How often are branded builds reissued?
Ask sales for the cadence that applies to your agreement rather than assuming a schedule from this page.
Can I force customers onto a new build?
Not retrospectively. Plan releases so old builds keep working for a reasonable period.
Where do I publish the checksum?
Wherever you publish the download. It lets a customer confirm the file is the one you shipped.