Party games · host, player & shared-display experiences
Mudoinkle brings three original party games into one playful browser experience, with clear paths for the host, each player, and the screen everyone shares.
Public staging. The preview explains the games without claiming completed multi-device room acceptance or a production launch.
Three games, three different play patterns
These live public previews make each game model easy to compare without an account. Accepted source includes separate host, player, and shared-display routes; complete multi-device room acceptance is still pending and is not represented by these preview captures.
Open the current public experience
Live public staging preview
The live public sample presents the image prompt, competing captions, and next-prompt action in the same visual rhythm a player will meet during the game.
Visible result: the caption-battle decision pattern is understandable without an account.
Capability demonstrated: translating a social prompt-and-response game into a branded, self-explanatory interaction loop.
Live public interactive preview
Witigglies exposes the timer, secret word, forbidden clues, and next-card action together so the person holding the phone knows what to protect and what to do next.
Visible result: a pass-and-play round with a distinct information hierarchy and control model.
Capability demonstrated: touch-first information hierarchy for a private, single-device play pattern.
Live public interactive preview
List Off puts the active topic, accepted answer, next-answer action, and new-category control into one fast scan for players following the round.
Visible result: a real-time category loop that reads differently from the other two games.
Capability demonstrated: keeping topic, accepted input, score, and round controls understandable in one fast-moving state.
Cyvexly contribution
Cyvexly developed the product identity, responsive public experience, game catalog, and distinct host, player, display, account, and room-state surfaces needed by a multi-device party platform.
This is a built product-system capability example, not a client engagement or a claim of revenue, adoption, or measured business results.
Shown and supported
Current limits
Used a shared game catalog and route system so three different play models still feel like one product
Separated public join/display paths from Clerk-protected host and account areas
Designed PostgreSQL for durable business records and Render Valkey for authoritative live-room state, with migration and health gates around deployment
From product complexity to a clear scope
Roles, states, data, integrations, security, migration, and proof requirements shape the build. Cyvexly confirms the right path and pricing in writing after discovery.
CYVEXLY STUDIO
