Wildcard
A real-time browser-based multiplayer card game for 2–10 players, built around color/number matching, action cards, and wild cards. Create or join a table with a room code — no installs, no accounts required.
- 2–10 Players Multiplayer room capacity
- Real-time Socket.IO live synchronization
- 3 Modes Create, Join & Play vs Computer
- Monorepo Shared engine across client & server
The Problem
Most multiplayer card games require account creation, app downloads, or complex setup before players can join a match. The friction of onboarding kills spontaneous play; by the time everyone installs the app and creates accounts, the moment has passed. Building a real-time multiplayer experience that works instantly in a browser, stays synchronized across devices, and handles edge cases like disconnections, reconnections, and bots requires careful architecture around state management, WebSocket communication, and game logic distribution.
What Was Built
Built Wildcard as a full-stack multiplayer card game monorepo using pnpm workspaces. The shared package contains the pure game engine; card validation, effect application, turn ordering, and bot logic ensuring the same rules power both the client and server. The Fastify backend orchestrates game rooms, manages Socket.IO connections, schedules bot turns, and persists room state to Redis. The React frontend delivers smooth animations via GSAP Flip and timeline, responsive layouts with Tailwind CSS, and real-time updates through Socket.IO. Three play modes are supported: create a private table and share a room code, join an existing table by code, or play instantly against computer opponents.
Highlights
- Real-time multiplayer with room codes — no accounts or installs needed
- Create Table, Join Table, and Play vs Computer modes
- Full action card system: Skip, Reverse, Draw Two, Wild, Wild Draw Four
- Scoring system tracking points per round and cumulative totals
- GSAP-powered card animations for draw, play, and shuffle effects
- Redis-backed room persistence enabling server restarts without data loss
- Play vs Computer mode with bot opponents
- Socket.IO real-time communication with automatic reconnection
- Monorepo architecture with shared game engine consumed by client and server
Engineering Decisions
The core challenge was maintaining perfect game state synchronization across multiple connected clients under unreliable network conditions. Every card play, draw, and action effect must be validated server-side, broadcast to all players, and rendered identically on every screen; even when players connect mid-game or reconnect after a disconnect. The solution involved a single-source-of-truth game engine in the shared package, server-authoritative state management, optimistic UI updates on the client, and Redis persistence so rooms survive server restarts. Bot scheduling added another layer of complexity; computer opponents must respect real turn timing without blocking the event loop.
Architecture
- React 18 + ViteClient UI with GSAP animations
- Socket.IOReal-time bidirectional communication
- Fastify ServerRoom orchestration & game validation
- RedisRoom state persistence & recovery
In Development
Scout
AI-native startup job-search workspace. Save startups and jobs from anywhere on the web and Scout researches each company with AI, matches open roles against your CV with semantic search, and carries you from application through outreach in one place.
In Development
AccountOS
Programmable virtual account infrastructure built on Nomba, enabling rule-driven automation, immutable ledgers, treasury management, and auditability for fintech products.
AfroGoods
B2C marketplace built for a Canadian client, enabling customers across the diaspora to shop African food products online, with a built-in advert hub for community listings.