Decked Out blends modern Android tooling, cloud services, and a low-latency backend into a cohesive architecture that keeps multiplayer matches responsive and reliable.
Native client on modern Android
The Decked Out client is built in Kotlin, taking advantage of coroutines, null-safety, and modern Android APIs. This keeps the codebase concise and maintainable while delivering a smooth, responsive game experience on current Android devices.
Reactive UI for cards and boards
Jetpack Compose powers the game interface—from hands of cards to spell effects. UI is described declaratively, so the view stays in sync with game state and can be iterated on quickly without fragile XML layouts.
Scalable infrastructure
AWS hosts the backend services that keep matches running. Managed compute, storage, and networking mean the system can scale with player demand while keeping latency low and uptime high.
Offline-ready local state
Room provides a structured local database for cards, decks, and player metadata. It gives Decked Out a reliable cache so players can browse data instantly and keep progress even when their connection is unstable.
Real-time multiplayer engine
A Python backend with WebSockets coordinates live matches. Players send and receive game events over persistent connections, keeping turns, card plays, and combat effects synchronized with minimal overhead.
Storefront Integration
WooCommerce powers the Monte Cook Games online storefront and product catalog. Digital Deckbox integrates with the WooCommerce REST API to read purchases and product metadata, so a player’s in-app content mirrors what they own on the store. Orders and line items are mapped to decks and campaigns, allowing new purchases to unlock the corresponding card packs in Digital Deckbox without manual provisioning.
Source control & collaboration
GitHub hosts the Digital Deckbox codebase, providing version control, pull requests, and code reviews. Branch protection and issues keep changes organized and make it easy for the team to collaborate on features, fixes, and documentation without losing track of progress.
The client, backend, and deployment stack form a single pipeline: developers work in Android Studio and Jetpack Compose, commit changes through GitHub, and deploy services to AWS. Players interact with a polished mobile client while WooCommerce connects everything to the Monte Cook Games storefront.
This diagram summarizes the flow from development tools to runtime infrastructure, highlighting how each technology contributes to a cohesive experience.
