Casino Days app teardown
Nothing to install. Casino Days runs in the browser on a phone, which means 9 taps to get money moving and a login every time Safari decides to clear itself out.
The numbers
None
PACKAGE
18 of 49 ship nothing
9
TAPS IN THE BROWSER
Board median is 6
1
FRICTION SCREENS
Inserted into the flow
C$10
MINIMUM DEPOSIT
Floor across the rails listed
The withdrawal flow, tap by tap
1 of those 9 screens are not carrying information. They are asking again. Across the board, 27 of 49 cashout flows do some version of this, and the industry-wide effect is the point of the design rather than a side effect of it.
Same job in a mobile browser takes 9 taps here, against a board median of 6. Across the whole board the app version averages 5.3 taps and 11 of 31 packages went through 40 sessions without a crash.
GOOD
- Chat sits in the mobile site and it answers at 3am
- 400 live tables, streamed to a phone
NOT GOOD
- No package to install, so it is the browser or nothing
- Cashout flow carries a pre-ticked reversal box
Getting paid
| Rail | Minimum in | Out | Minimum out |
|---|---|---|---|
| Interac e-Transfer | C$10 | 36 hrs | C$10 |
| MuchBetter | C$10 | 12 hrs | C$10 |
| Crypto (BTC, ETH, USDT) | C$10 | 12 hrs | C$20 |
| iDebit | C$10 | 24–48 hrs | C$20 |
| Visa/Mastercard | C$10 | 2–5 days | C$50 |
Typical wait to a bank account here is 36 hrs. Rail timings are the operator's own published figures; the tap counts above are ours. The rail pages hold the same question one payment method at a time.
All of it measured the same way on every operator on this board, which is the only thing that makes any of these numbers comparable.
