Sixer appUpdated 27 July 2026 · 16:42 IST
Editorial photograph of a stadium pavilion exterior for the app hero.
Sixer app

Sixer does not ship a separate mobile app — the desk works through the first-party route.

Some readers ask whether Sixer has a mobile app. The honest answer is: Sixer is an editorial matchday desk, not a platform operator. The desk works on the first-party access route the platform you choose maintains for editorial readers.

How the access works

How Sixer routes a reader to the platform.

The Get Started button resolves through the first-party route — the same URL the platform maintains for the editorial relationship between itself and a reader. Sixer does not insert an intermediate landing page between the reader and the platform.

On desktop

The header-right Get Started button carries the first-party access route; rel attributes follow the editorial policy that nofollow noopener noreferrer with a sponsored relationship declaration.

Sponsored linkFirst-party route

On mobile

The mobile drawer exposes the same Get Started button as a single CTA. The persistent sticky CTA on mobile is one button only — labelled PLAY NOW — and points to the same first-party route.

Single CTAPLAY NOW

In editorial copy

Where an editorial section carries commercial intent (captain call, points-ledger, app access checkpoint), a contextual affiliate CTA resolves through the same first-party route. Ordinary internal navigation never carries the route.

Commercial CTAs onlySame URL

In policy pages

The state eligibility, responsible play and terms pages expose the route only as an editorial CTA — never as a recommendation. A reader who does not want a commercial path can read all the editorial pages without ever clicking it.

Editorial onlyOptional
Read on mobile

Read the desk on mobile.

Sixer is built to read cleanly at 320–430px widths. The desk's editorial pages hold their reading rhythm on a phone.

Sticky header

The header stays at the top of every page so the menu and search controls are always one tap away.

Single persistent CTA

On mobile, one persistent CTA — labelled PLAY NOW — appears only after the reader scrolls past the hero. It uses the first-party access route.

Reading-friendly typography

Nunito Sans at a 17–18px body size with 1.65–1.8 line height. Headlines wrap to natural word boundaries; no character-by-character breaking.

FAQ

Sixer app — short answers.

Does Sixer publish a mobile app?
No. Sixer is an editorial matchday desk; the desk reads on the same mobile web renderings every other site uses. Where a reader wants a platform app, the platform publishes its own.
Where is the first-party access route defined?
In the .control-room/affiliate-contract.json the editorial desk operates under. The route resolves to a single URL on the platform's own infrastructure.
Does the link rel mean anything?
rel="sponsored nofollow noopener noreferrer" declares the editorial-policy nature of the link. It does not change the user experience; it informs the platform and search-engine crawlers about the commercial relationship.
Read on mobile

How the desk reads on mobile.

Sixer's editorial pages are built mobile-first. Reading the desk on a phone at 320–430px widths is the editorial default.

Sticky header

The header stays at the top of every page so the menu and the CTA controls are always one tap away.

Single persistent CTA

A single persistent CTA — labelled PLAY NOW — appears only after the reader scrolls past the hero.

Reading-friendly typography

Nunito Sans at 17–18px body size, 1.65–1.8 line height. Headlines wrap to natural word boundaries.

Reading on tablet

Reading on tablet.

Sixer's editorial pages are built to read cleanly at tablet widths (768–1024px). Reading on a tablet is the same editorial scope as reading on desktop.

Grid reads at half-width

The chapter rail collapses at half-width on tablet; the desk becomes a wider two-column read with the editorial content on the left and the chapter rail on the right.

Tables remain horizontal-scroll

The points-ledger and tournament-calendar tables remain horizontal-scrollable on tablet; the desktop read stays the same.

Tap targets stay large

Tap targets are at least 44px tall on tablet; the menu, the rail cards and the CTA buttons stay readable and clickable.

Reading the access route

Reading the first-party access route.

Sixer's first-party access route is the editorial way the desk hands a reader to the platform. The route is a single URL across the entire site.

A single URL

The first-party access route is one URL; Sixer does not insert an intermediate landing page between the reader and the platform.

Sponsored, nofollow

The link is sponsored, nofollow, noopener, noreferrer. The rel attributes declare the editorial-policy nature of the relationship.

Same URL, every CTA

Every Get Started button — desktop, mobile drawer, sticky CTA — points to the same first-party access route.

PLAY NOW
First-party route · 18+ · state eligibility applies