Back to work Wikibet: Case Study iGaming · Web · Mobile Web
Wikibet Platform UX Overhaul
iGaming · Web · Mobile Web // 2023

Wikibet

A full platform UX overhaul: rebuilding a high-density casino and sports betting product for clarity, consistency, and mobile parity.

Role UX / UI Designer
Tools Figma · Photoshop
Type Professional Case Study
Platform Web · Mobile Web

A platform rebuilt
from the ground up

Wikibet is an online casino and sports betting platform serving players across desktop and mobile web. As the sole full-time designer, I was responsible for the full scope of UX and UI design, covering the core interface, the component system, and marketing materials.

The platform had an existing desktop interface but no coherent design system, inconsistent components across screens, and a mobile experience that was largely non-functional. Critical features like account management and withdrawal flows were missing entirely.

My work involved rebuilding the interface from the ground up: establishing a unified design system, redesigning core desktop screens, and designing the full mobile experience as a first-class product rather than an afterthought.

My Role
UI Design
UX Design Design Systems Marketing Assets
Tools
Figma
Photoshop Illustrator
Scope
Full platform redesign
Design system Desktop & mobile web

Three problems,
one broken product

Wikibet's existing interface had three fundamental issues that impacted the platform's usability and trustworthiness.

No mobile feature parity
Mobile users could browse games but little else. Critical features including account management, security settings, and withdrawal flows were either absent or inaccessible on mobile. For a platform handling real money transactions, this wasn't a minor gap. It was a product failure.
Inconsistent interface system
Without a unified component library, screens felt disjointed. Navigation patterns shifted across sections, form interactions were inconsistent, and visual hierarchy was unclear. This was particularly problematic in high-stakes contexts like deposits and withdrawals.
Fragmented account management
Profile settings, security, notifications, and withdrawal functions were scattered across the interface with no central hub. Users had no clear mental model of where to find critical account functions, creating friction in moments that required trust.

Foundation first

Before redesigning any screens, I established a unified component library covering typography, color tokens, buttons, form fields, navigation states, and notification patterns. Having a system in place ensured consistency across a product with hundreds of screens and two platforms, and gave developers clear implementation guidance throughout the build.

Wikibet Design System and Style Guide Wikibet design system: color tokens, typography, spacing, components, and patterns

Hierarchy over
density

The original homepage suffered from competing visual weight across elements. The navigation, promotional banner, game categories, and payment strip all demanded equal attention, making it difficult for users to orient themselves or find games quickly.

The redesign introduced a collapsed icon sidebar to reduce persistent navigation weight, cleaner category labeling, improved game card sizing for better scannability, and a clearer visual hierarchy that guides users from the promotional banner down through game discovery naturally.

Original Wikibet homepage Original interface: dense layout with unclear visual hierarchy
Redesigned Wikibet homepage Redesigned interface: collapsed navigation, clear content hierarchy

Modals out,
pages in

The original authentication experience was handled through modal dialogs, a pattern that worked reasonably on desktop but created significant usability problems on mobile, where limited space compressed form fields, reduced error message visibility, and made the password recovery sequence difficult to follow.

The redesign replaced modals with dedicated full-screen pages for login, registration, and password reset, giving each step room to breathe, improving inline validation visibility, and reducing cognitive load during what is often a user's first interaction with the platform.

Original modal-based authentication Original: modal dialogs on mobile, limited space and poor error visibility
Redesigned authentication flow Redesigned: dedicated full-screen pages with clear validation states
Password reset flow sequence Password reset sequence: request, confirmation, new password

Built from nothing

Mobile users had no ability to withdraw funds. The only option available was a transaction history table. For a platform handling real money, this was a critical functional gap that forced users to desktop for one of the most important account actions.

The redesign introduced a complete mobile withdrawal flow: available balance display, quick amount presets, manual entry with validation, payment method selection, a confirmation step with full transaction summary, and an error state preventing withdrawals above available balance. Every step was designed to give users clarity and confidence when moving real money.

Withdrawal flow: full sequence Left to right: old state (transaction history only), amount entry, validation error, confirmation, transaction history

One hub for
everything

Account management on the original platform had no dedicated home. Profile information, security settings, notifications, and withdrawal functions were accessed through scattered interface elements, giving users no clear mental model of where to find or change critical account information.

The redesign introduced a centralized settings hub with four clearly defined sections: Profile, Security, Notifications, and Withdrawal, all accessible from a single location. Each section uses a consistent accordion pattern that reveals detail without navigating away, keeping users oriented throughout. Contextual guidance was added for restricted actions like account deactivation, reducing unnecessary support contact.

Settings: Security section Security settings: password change with contextual guidance
Settings: Notifications section Notifications settings: granular control with clear labeling

Mobile as a
first-class product

Mobile was designed as a complete parallel product, not an adaptation of the desktop interface. Every core user journey, including game discovery, account management, financial transactions, authentication, and legal compliance, was designed natively for mobile with appropriate interaction patterns, touch targets, and information hierarchy.

The result is a mobile experience with full feature parity across all critical platform functions.

Shipped and
measured

The redesigned platform was fully implemented and launched. The overhaul resulted in measurable conversion improvement, attributed primarily to the introduction of mobile financial flows that previously didn't exist, and the reduction of friction in core user journeys like authentication and account management.

Beyond conversion, the project established a unified design system that gave the development team a consistent implementation reference across a product with hundreds of screens and two platforms, reducing design ambiguity and supporting faster future iteration.

Designing a system from scratch inside a live product taught me that consistency is infrastructure. It's invisible when it works and painful when it doesn't. The most impactful decisions weren't visual; they were structural. Defining how components behave, how screens relate, and how flows connect was what made the visual work land.

Overview The Problem Design System Homepage Authentication Withdrawal Flow Settings Mobile Outcome