Flow overview
Two of them are the happy paths inside the prototype. The other two are the edges I kept thinking about: how players find rewards on their own, and what happens when something breaks.
Minimised component catches the eye
Player taps to open it
Full info appears in context
Player taps Start Free Spins
Active state confirms it, the counter is live and visible
The default path. The player sees it, opens it, uses it, finishes.
Note to self
Present without getting in the way. It sits at the bottom of the screen, with a fallback for providers that already use that area
Player taps the gift icon in the top menu
The rewards panel opens with the eligible offers
An eligible game is shown with a clear preview
Player taps into the game
The component is already there when the game loads
The player goes looking. Rewards page first, then the game.
Note to self
Some players look for rewards in the gift icon, not inside the game. Both entry points should land them in the same place
Error visible in the minimised state
Player opens it to see why
Clear CTA: 'Adjust bet to £2.00 or less'
Player lowers the bet inline
Component goes back to available, the player keeps going
Bet too high. The CTA tells the player how to fix it.
Note to self
The error says what went wrong and what to do about it. It tries to solve the problem, not just describe it
Timer state triggers the warning at the threshold
Amber chip and soft copy appear
Player is informed, not pushed
Player chooses to act, dismiss, or be reminded later
Expiry is handled with care, whatever the choice
Urgency without pressure.
Note to self
Responsible gaming lives inside the copy, not as a disclaimer at the bottom. 'No rush, only use them if you want to'
