Flow overview

Four ways a player meets Free Spins

I mapped each flow as a product behaviour, not just a screen journey. Each one connects what the player is trying to do with the business outcome, the risk to manage and the metric I would use to validate success.

Player behaviour

What the player notices, understands and decides during the reward journey.

Product outcome

How the flow supports activation, completion, retention or reduced confusion.

Validation

Which metric would show whether the flow is working after launch.

Minimised component creates reward awareness during play

Player notices Free Spins without leaving the game

Player opens the component to understand eligibility and value

Player taps Start Free Spins from the expanded state

Active state confirms progress, remaining spins and winnings

01Prototype flow

In-game discovery

The default path. The player notices, opens, understands and activates the reward.

Player behaviour

The player notices an available reward during the current session and understands that it can be used now.

Product outcome

Increase Free Spins discovery and activation while reducing the chance of the player using their own money by mistake.

Success metrics

Discovery rateActivation rateBonus completion rate

Design decision

The component needs to be 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

Rewards panel shows available Free Spins and eligible games

Player understands where the reward can be used

Player enters an eligible game from the reward journey

The in-game component appears when the game loads

Gift icon entry

The player actively looks for rewards, then moves from the rewards area into an eligible game.

Player behaviour

The player uses the existing reward mental model to find Free Spins and move into an eligible game.

Product outcome

Connect the in-game component to the wider rewards ecosystem and support return-to-game behaviour.

Success metrics

Eligible game entry rateReward engagementSession return rate

Design decision

Some players look for rewards in the gift icon, not inside the game. Both entry points should connect to the same reward journey.

Error is visible from the minimised state

Player opens the component to understand what changed

Clear CTA explains the rule: Adjust bet to £2.00 or less

Player lowers the bet and stays in the journey

Component returns to available and the player can continue

03Prototype flow

Error recovery

The player is blocked by a rule, but the component explains the issue and helps them recover.

Player behaviour

The player understands why they are blocked and can fix the issue without abandoning the reward.

Product outcome

Reduce frustration, bonus abandonment and support contacts caused by unclear bonus restrictions.

Success metrics

Error recovery rateSupport contact reductionAbandonment rate

Design decision

The error should say what went wrong and what to do about it. It should solve the problem, not just describe it.

Expiry threshold triggers a softer warning state

Amber chip and clear copy explain the time left

Player can choose to act, dismiss or continue playing

Expiry messaging remains factual and transparent

The state updates calmly if the reward expires

Expiring soon

The player receives clear expiry information without pressure or manipulative urgency.

Player behaviour

The player understands the reward is close to expiry and can make an informed choice.

Product outcome

Support reward completion without creating pressure, dark patterns or irresponsible urgency.

Success metrics

Expired bonus rateCompletion rateDismissal rate

Design decision

Responsible gaming lives inside the interaction and copy, not as a disclaimer at the bottom. The UI should inform, not push.