Method
AppScore v1: how the score is built and what it leaves out
AppScore v1 gives a betting app a score out of 100 from six weighted criteria, after one gate: the operator's licence must be active on the GRAI register. Weights are 25, 15, 10, 30, 10 and 10. An operator with an unchecked criterion gets no score. The score is recalculated monthly and when an input fact changes. It does not measure odds or payout speed.
Editorial team · checked
The gate and the six criteria
The gate comes first: no active licence on the register, no score.
| Criterion | What earns points | Points |
|---|---|---|
| C1 Irish listings | A listing in the Irish App Store (13) and on Google Play (12) | 25 |
| C2 Transparency | Developer matches the licensee (5), App Privacy section (5), Data safety section (5) | 15 |
| C3 Freshness | Updated within 90 days (10), 91 to 180 days (5), older (0) | 10 |
| C4 Controls | Deposit limit, time limit, time-out, self-exclusion, link to help: 6 each | 30 |
| C5 Payments | 2 per documented method from a closed list of five | 10 |
| C6 Features | Streaming 3, cash out 3, bet builder 2, notification control 2 | 10 |
In short: points reward what is documented, and the total is 100.
The closed payment list
C5 counts five methods only: debit card (Visa Debit and Mastercard Debit count as one), Apple Pay, Google Pay, PayPal, and bank transfer or Open Banking.
Credit cards are barred in Ireland (credit card ban) and earn nothing.
In short: five methods at 2 points each.
Platform scores and unknown values
A platform score is the share of the applicable maximum. iOS has no Data safety section and no Google Play listing, so its maximum is 83. Android has no App Privacy section and no App Store listing, so its maximum is 82.
Unknown means not scored: an operator is assessed only when all six criteria are checked.
In short: iOS out of 83, Android out of 82; unknown values block a score.
Worked example with invented numbers
This example describes no real operator.
| Criterion | Invented facts | Points |
|---|---|---|
| C1 | Both listings present | 25 |
| C2 | Developer matches, App Privacy present, Data safety missing | 10 |
| C3 | Last update 120 days ago | 5 |
| C4 | Four of five controls documented | 24 |
| C5 | Three methods documented | 6 |
| C6 | Streaming, cash out, notification control | 8 |
| Total | 25 + 10 + 5 + 24 + 6 + 8 | 78 / 100 |
In short: the total is shown as text, such as 78 / 100, never as stars.
What the score leaves out
- Odds and prices.
- Withdrawal speed, which we do not test.
- Ease of use and customer service.
- Offers and bonuses.
- Store ratings: they are not an input and are not shown as our own (why).
In short: AppScore measures documentation, not how good a bet is.
Recalculation and reproduction
Scores are recalculated monthly and whenever an input fact changes. The script and a CSV of inputs are meant to be published with each results table (results).
In this test build no operator has been scored: inputs are Not checked, and the script and CSV are not yet generated.
In short: anyone with the inputs should reach the same number.
18+ only. Gambling can be addictive – play responsibly. Set limits, take breaks and never bet more than you can afford to lose. Free 24/7 support: Gambling Awareness Trust helpline 1800 936 725 · gamblingcare.ie.
Keep going