How to download the Odds app from the official app stores
The Odds app is the editorial desk's mobile companion. The download flow is the standard app store download — the reader visits the official app store, searches for "Odds Esports", and follows the standard download flow. The download page is the editorial desk's read on the download flow, with the editorial verification chain published with the page footer.
What the download page does
The download page directs the reader to the official app stores. The Android download directs the reader to the Google Play Store. The iOS download directs the reader to the Apple App Store. The regional mobile lanes direct the reader to the regional app stores. The download page does not host the app — it directs the reader to the official app stores, where the app is hosted by the official app store.
The download page is built to be accessible to readers aged 18 and over. The download page does not require a subscription, does not publish betting lines, and does not promote a particular team's chances. The download page is separate from the operator account flow, and the editorial verification chain is published with the page footer.
How to download the app
The download flow is the standard app store download. The reader visits the official app store, searches for "Odds Esports", and follows the standard download flow. The app is built to be small, fast, and accessible. The app is built to work offline, with the content cached locally for offline reading.
The download page is built to be transparent. The download page does not collect any information beyond the editorial desk's published RSS feed, the editorial sitemap, and the editorial verification chain. The download page does not share any information with the operator account flow, and the operator account flow does not share any information with the download page. The two are separate by design.
System requirements
The Odds app is built to work on every major mobile platform. The Android app requires Android 9.0 or later. The iOS app requires iOS 14.0 or later. The regional mobile lanes require the regional mobile platform's standard operating system. The app is built to be small, fast, and accessible. The app is built to work offline, with the content cached locally for offline reading.
The app is built to be accessible to readers aged 18 and over. The app is built to be accessible to readers using screen readers, keyboard navigation, and touch devices. The app is built to be accessible to readers using the editorial desk's accessibility layer.
Storage and bandwidth
The Odds app is built to be small and fast. The app downloads in under 30 seconds on a typical mobile network. The app uses under 50MB of storage on a typical mobile device. The app uses under 5MB of bandwidth per day on a typical mobile plan. The app is built to work offline, with the content cached locally for offline reading.
The app is built to be transparent about its storage and bandwidth use. The download page documents the storage and bandwidth requirements, and the verification chain is published with the page footer. The app is built to be accessible to readers aged 18 and over, and to readers using the editorial desk's accessibility layer.
Editorial verification chain
The download page is published with the editorial verification chain. The editorial verification chain documents the source, the verification date, the verification result, and the editorial context. The editorial verification chain is published with the page footer, and the editorial verification chain is available on request through the contact desk.
The download page is open to all readers aged 18 and over. The download page does not require a subscription, does not publish betting lines, and does not promote a particular team's chances. The editorial read is published with the verification chain documented in the page footer, and the source dossier is available on request through the contact desk.
What the editorial desk reads on this page
The editorial desk reads three working documents on every page the desk publishes. The published record is the editorial layer the broadcast can't carry — the source, the verification date, the verification result, and the editorial context. The editorial analysis is the editorial timing the broadcast can't carry — the editorial read, the editorial verification chain, the editorial context. The editorial coverage is the editorial follow-up the broadcast can't carry — the editorial window, the editorial cadence, the editorial follow-up.
The editorial read pairs the published record with the editorial analysis and the editorial coverage. The editorial read is the editorial layer the broadcast can't carry, and the editorial verification chain is published with the page footer. The editorial read is built to be accessible to readers aged 18 and over, and to readers using the editorial desk's accessibility layer.
The broadcast studio carries the editorial layer
The broadcast studio is the editorial layer the broadcast can't carry. The studio carries the editorial read, the editorial verification chain, and the editorial context. The editorial read is published with the editorial verification chain, and the editorial verification chain is published with the page footer.
The verification chain is the editorial record
The verification chain is the editorial layer the operator's marketing channel can't carry. The chain documents the source, the verification date, the verification result, and the editorial context. The chain is published with the page footer, and the editorial verification chain is available on request through the contact desk.
How the editorial verification chain is documented
The editorial verification chain is documented across four layers. The source layer identifies the official channel the editorial desk cross-checked against — typically the operator's official documentation, the league's official channel, the team's official social media, or the broadcast partner's official bracket. The verification date layer identifies when the editorial desk cross-checked the source. The verification result layer identifies the editorial desk's conclusion — confirmed, refuted, or unresolved. The editorial context layer identifies the editorial reasoning behind the result.
The editorial verification chain is built to be transparent. The chain is published with the page footer, and the chair is available on request through the contact desk. The chain is built to be accessible to readers aged 18 and over, and to readers using the editorial desk's accessibility layer.
What the page covers in three working documents
First, the published record — the source, the verification date, the verification result, and the editorial context. Second, the editorial analysis — the editorial read, the editorial verification chain, the editorial context. Third, the editorial coverage — the editorial window, the editorial cadence, the editorial follow-up. The three documents are the editorial layer the broadcast can't carry, and the editorial read is published with the editorial verification chain.
The editorial desk's read on the broadcast
The editorial desk reads the broadcast the way the casters read the script. The desk reads the editorial layer, the editorial verification chain, and the editorial context. The editorial read is the editorial layer the broadcast can't carry, and the editorial verification chain is published with the page footer.
What the editorial desk signs up to
The desk verifies every download page workflow against the official app store, the developer's official app documentation, and at least one independent source. The verification chain is published with the page footer.
What readers ask the desk most
How do I download the Odds app?
Visit the official app store, search for "Odds Esports", and follow the standard download flow. The download page directs the reader to the official app stores.
What are the system requirements?
The Android app requires Android 9.0 or later. The iOS app requires iOS 14.0 or later. The regional mobile lanes require the regional mobile platform's standard operating system.
How much storage does the app use?
The app uses under 50MB of storage on a typical mobile device. The app uses under 5MB of bandwidth per day on a typical mobile plan.
Does the app work offline?
The app is built to work offline, with the content cached locally for offline reading. The verification chain is published with the page footer.