Stardust Casino app teardown
The short version: 7 taps to withdraw, 125 MB on disk before it unpacks, 1.5 s to open. Everything below is how we got those three numbers.
The numbers
125 MB
INSTALL SIZE
Over the 115 MB board median
1.5 s
COLD START
19 of 31 on the clock
0
CRASHES / 40 SESSIONS
Both handsets, clean
7
TAPS TO WITHDRAW
Board median is 5
The withdrawal flow, tap by tap
2 of those 7 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
- Same build on both stores, no Android afterthought
- No crash in 40 sessions on either handset
- Chat is in the app and it answers at 3am
- 80 live tables, streamed to a phone
- The app cuts 2 taps off the same job in a browser
NOT GOOD
- 7 taps to a submitted withdrawal, against a board median of 5
- 125 MB down, roughly 263 MB once it has unpacked
- Cashout flow carries a pre-ticked reversal box
- 2 screens exist only to give you a way out of leaving
What the app does that the site does not
- Cashout drops from 9 taps to 7
- Biometric login instead of a password field on a wet screen
- Chat opens inside the app rather than in a new tab
- Deposit and session limits live in settings, not five clicks into an account page
- Live tables hold the stream through a network handover
The tap saving is the measurable one: 9 in a browser, 7 in the app, for identical work.
Getting paid
| Rail | Minimum in | Out | Minimum out |
|---|---|---|---|
| Interac e-Transfer | C$10 | 14 hrs | C$10 |
| PayPal | C$10 | 24 hrs | C$20 |
| Visa/Mastercard | C$10 | 2–5 days | C$50 |
| iDebit / Instadebit | C$10 | 1–2 days | C$20 |
| MuchBetter | C$10 | 24–48 hrs | C$10 |
Typical wait to a bank account here is 14 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.
Those figures are what the handset reported. We are not scoring the company behind the app, only what the app did on two phones over three weeks.
