paidAffiliate disclosure. The partner link in the masthead and in the bands beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. That matters on this desk in particular: the subject is what a device hands to an app and what a reader can refuse, and this site’s own revenue depends on a reader opening an account. No operator and no app is named, rated or recommended anywhere on this site.
The Handset / Who builds it
The publisher and the store
Who builds it
Three parties stand between a player and the app: whoever writes the code, whoever holds the store account and submits the build, and the store that decides when - or whether - it is installable.
App stub
- Publisher
- the entity named on the store listing
- Builder
- often a vendor, named nowhere a player sees
- Store account
- one, and its loss is the app’s loss
- Builds a year
- 16, at 2.4 days in review each
- A year in review
- 38.4 days, 41.9 with rejections
the promptA question the device asks once, and an answer you can change at any time
the tokenWhat keeps a phone signed in, and how long it lives without an open
the buildA numbered version of the app, and the only part of the product an update can change
Direct answerA gambling app is usually built by a vendor and published by an entity that holds the store account. The player sees only the listing: a name, an icon, an age rating and a category. The builder is invisible, the store account is the single point of failure, and a build spends a measurable part of the year waiting to be reviewed.
Question who actually ships the app I install?Published by the entity on the store listing, not necessarily the operatorBuilt by frequently a vendor; rarely visible to a playerGated by the store, which reviews every buildSample app 16 builds a year at 2.4 days in review
The three parties
party 01The entity on the listing
The listing names a legal entity, and that name is where a reader can check who is behind the app. It is
not always the brand on the icon, and it changes when a group reorganises. Cycle 24 of this series owns that
question in full - finding the entity and the licence - so this desk only names it as the thing a store account
is tied to.
party 02The builder behind the entity
The code is commonly written by a supplier that builds apps for several operators. That supplier ships the
same navigation, the same permission set and often the same lobby to more than one brand, which is why two
different operators’ apps can feel identical while their terms differ. Nothing in the listing tells a
player which supplier built it.
party 03The store account
The store account is a single asset: a lost or suspended account takes the app off every phone at once,
and no website URL can replace it. That is the one risk in this desk that has no fallback for the player,
which is exactly why the website remains the container that cannot be removed by a third party.
- A build is finished and given a number: the sample app is on build 16 of the year.
- It is submitted with its declaration and waits in the review queue - 2.4 days on this sample.
- About 22.0% of submissions come back needing a change, adding roughly a day each.
- The build becomes installable, and every device is offered it; the oldest supported build moves up one.
- A device above the floor keeps working without updating; a device below it is told to update before it can open.
A year of the app in a review queue
builds a year: 16 (four a quarter)
review per build: 2.4 days
review, clean: 16 x 2.4 = 38.4 days
rejections: 22.0% of 16 = 3.5 builds, about 1.0 day each
review, with rejections: 38.4 + 3.5 = 41.9 days a year
The app spends 41.9 days of the year - about a ninth of it - waiting for a
decision that is not the operator's to make.
The consequence a player feels. A fix that exists in the code is not in the player’s hands until it clears that queue, and a device
that skips an update keeps the old behaviour until it is forced forward.
16 builds one account 41.9 days no fix is instant