Wazbee Casino

Context

Production JER-TEAM iGaming product (casino + sportsbook). My role at Softrocket: large share of the public frontend — architecture, core flows, shipping with design — in the same family as Welle and RoySpins.

Problem

Full casino client under real traffic: multi-step registration, fiat/crypto cashier, bonuses, KYC, localization, realtime — without a sluggish lobby.

Decisions & tradeoffs

• Aside outlets + lazy routes instead of full-page cashier/account navigation — panels stay on the lobby shell.
• NgRx for user/balances/bonuses/finance instead of prop-drilling across lobby and cashier.
• OnPush + lazy modules on heavy paths instead of eager loading the whole lobby.
• Keystone CMS for promos instead of hardcoding marketing content in releases.

What I built

• Frontend architecture: lazy-loaded routes, auth guards, preloading strategy, aside outlets for cashier / account / support.
• Branded lobby: sidebar, promo blocks, trust strip, category filters (Hot / Live / Providers), game card grids.
• Adaptive multi-step registration (simple vs full) with NgRx sign-up store, region/bonus-aware banners, validation.
• Cashier and payout UI: payment methods, amount forms, multi-currency, active payment state in NgRx.
• Realtime layer with Socket.IO (chat / tournaments / notifications) wired into NgRx.
• PixiJS + Spine for branded animated UI pieces.
• Integrations: Keystone CMS content, Transloco i18n, Sumsub KYC WebSDK, Sentry, Angular service worker (PWA).
• Performance pass on lobby and game entry: lazy components, change-detection discipline, load-path cleanup.

Outcome

Live at wazbee.com — production traffic, full lobby-to-cashier product surface.