GVC Group — V6 Platform

Responsive Sportsbook Redesign

One responsive platform replaced separate mobile and desktop codebases across 10 betting brands — mobile-first, white-label, built to scale.

Responsive Design Mobile-First White-Label Sports Betting Design System
bwin V6 responsive sportsbook across mobile, tablet, and desktop
Role
Senior UX Designer (IC)
Team
4 Designers, Researcher, PM, Tech Lead
Timeline
6 Months (2017–2018)
Platform
Responsive Web (320px → 1920px)
Brands
bwin, Ladbrokes, Coral + 7 more

Overview

GVC ran separate codebases for mobile and desktop. Every feature built twice. Every bug fixed in parallel. Users switching between phone and laptop hit two different products. We replaced all of it with a single responsive platform serving 10 brands from one codebase.

I was one of four designers on the project. My focus areas were global navigation, the betslip, My Bets, sports market layouts and responsive behaviour across mobile, tablet and desktop. I owned these end-to-end — from early concepts through to production-ready specs and developer handoff. The wider team covered registration flows, promotions, account management and the CMS-driven content layer.

1
Responsive experience across all devices
10
Brands on one platform
Shared component framework
1
Codebase replacing separate mobile & desktop
The Challenge

Two platforms. Ten brands. Zero consistency.

Mobile and desktop were built independently — different navigation, different features, different release cycles. A fix for bwin didn't reach Coral. Users noticed every time they switched devices.

01

Dual codebases drifting apart

Every feature built twice. The two versions often diverged — different UI patterns, different market structures, sometimes different feature sets entirely.

02

Real-time odds with no layout instability

Prices change multiple times per second during live events. The UI had to update without causing layout shift or mis-taps on real-money selections.

03

White-label inflexibility

Brand expression was hard-coded. Partners couldn't configure or customise without engineering involvement. Theming needed to live at the token level.

Structure

Information architecture

Mapped the entire navigation structure across Sports Home, Live, Racing, Virtuals, My Bets, and Betslip — defining how content hierarchies shift between mobile and desktop.

V6 Sportsbook Information Architecture — navigation and page hierarchy
Responsive

One layout system, four breakpoints

Every page designed mobile-first across 320px, 768px, 1366px, and 1920px. Content reflows, columns shift, features adapt — but the experience stays consistent.

01
Mobile-first, thumb-friendly
Primary actions in the thumb zone. Bottom nav for core paths.
03
Progressive disclosure
Popular markets first. Expand into handicaps, props, and niche options.
04
Reusable components
Brand at the token level. Dark and light themes from one library.
Components

Modular component system

Built a reusable module library covering sports lobby, coupons, live events, betslip, and navigation. Each module defined across all breakpoints with responsive reflow behaviour.

bwin V6 module library — sports lobby, competitions, live event modules
Mobile

Key mobile screens

85%+ of traffic is mobile. Every screen designed for one-handed use — from live event browsing to bet placement to cash out.

bwin V6 mobile screens — Live, Match Details, Bet Slip, Virtuals, My Bets, Search, and more
White-Label

One framework, ten brand identities

Theming at the semantic token level — not a paint job. Structure and interaction patterns locked; colours, typography, and iconography owned by each brand. Brands feel distinct while sharing the vast majority of the codebase.

01

Locked — Structure & Interaction

Layout, spacing, responsive behaviour. Identical across every brand.

02

Themed — Design Tokens

Colours, typography, iconography via semantic tokens. Components consume tokens, never raw colour.

03

Flexible — Campaign Content

Promotional graphics and editorial content that varies per brand and per market.

Ten portfolio brands rendered on the same V6 responsive framework
Theming

Dark mode from the same tokens

bwin's flagship dark theme and Coral's light theme both built from the same semantic token set. Switch a theme, the entire product adapts — no component-level overrides needed.

bwin V6 dark mode — betting interface with dark theme across mobile screens
Outcomes

Impact

Unified responsive experience
One experience across mobile, tablet and desktop replaced separate builds
Consistent navigation & betting journeys
Users encountered the same patterns regardless of device or brand
Reusable component framework
A shared library of modules accelerated delivery across all brands
Multi-brand support
Ten brands served from a single white-label platform
Reduced duplication
Eliminated parallel mobile and desktop work, streamlining maintenance
Reflections

What I took away

01
Responsive isn't layout — it's content strategy. The hardest decisions weren't about columns. They were about what deserves prominence at each screen size.
02
White-label thinking forces better architecture. Designing for 10 brands simultaneously forced clean separation of structure from style.
03
Test the transitions, not just the endpoints. The most valuable insights came from watching users switch devices mid-session.
04
Speed and clarity aren't opposites. Betting users want to act fast but need to understand what they're betting on. Progressive disclosure solves both.
Next project

Designing the Group BetStation

Ladbrokes / Coral — Entain