Instant phone controllers
for indie games

Secret information, typed

Whisper to one player, broadcast to a role, reveal to everyone on a game event. A typed API instead of a hand-rolled state machine and a bug-hunt every phase change.

room.whisper(alice, { role: "werewolf" });
room.reveal("roles", { on: "phase.day" });
room.broadcast({ to: "gm", note: "..." });

Role-based controller layouts

Declare roles once — captain, engineer, gunner — and each phone renders the right controller. No per-role codepath, no shipping four UIs in one.

Phone as a physical prop

A dice roller with shake-to-roll. A hand-of-cards with tilt-to-peek. A sealed envelope that only unlocks on a game event. Drop-in modules that turn the phone from an input device into an actual game piece.

Built for the genres no SDK covers

Social deduction (Spyfall, Werewolf). Asymmetric co-op (Keep Talking and Nobody Explodes). GM'd tabletop (Blood on the Clocktower, Sheriff of Nottingham). Pick the genre; the primitives are the same — and they're the primitives nobody else ships.

Screen-reader compatible out of the box

Every button, prompt, poll, and HUD element announces itself correctly on VoiceOver and TalkBack. You write one game; blind and low-vision players can play it without you learning ARIA.

Motor-accessibility layouts

One-handed mode, dwell-to-click, large-target mode, and reduced-input mode (fewer simultaneous presses required). Each ships as a player-side toggle — your input handler doesn't change.

Colorblind-safe palettes by default

Controllers inherit WCAG-safe palettes with automatic variants for deuteranopia, protanopia, and tritanopia. No more "the red button and the green button look the same."

"Simplify controls" mode

A player toggle that collapses your full gamepad to a minimal set of single-tap inputs — perfect for motor disabilities, cognitive differences, or first-time players. Your code writes one input handler; dropcontroller maps the simplification. Accessibility is free.

Audience mode, drop-in

Viewers scan a QR in chat and join as audience: vote on events, throw in-game items, answer prompts. Jackbox's killer feature — now a one-line primitive you don't build per-game.

room.openAudience({ capacity: 10_000 });

room.onAudienceVote((e) => {
  // e.choice, e.count, e.totals
});

OBS overlays, out of the box

Controller inputs, poll results, leaderboards, player avatars — all available as transparent OBS browser sources. Paste the URL; ship production value. No After Effects, no custom overlay engineer.

Auto-clip from game code

Tag a moment in your game loop; get back a shareable 10-second MP4 or GIF. Every clip is a distribution event — for the game and for the player who made the play.

room.clip({
  label: "finisher",
  duration: 10,
});

Viewer → player funnel

A viewer taps a link in chat, scans a QR, becomes the next player in the stream. Every stream is a top-of-funnel acquisition event — for your game and for every other dropcontroller game they'll ever scan into.

Input heatmaps

A literal tap-density map over your controller layout. See that the jump button is too small, that B is getting mis-tapped for A, that nobody's finding the radial menu in under three seconds.

Session replay for bug reports

A player files a bug. You get the last 30 seconds of controller inputs, game-state events, and per-hop latency for that exact session. Sentry for gamepads — no "can you reproduce it?" email thread.

A/B test controller layouts

Ship two controller variants; keep the one that retains. No client code changes, no analytics SDK to wire, no stats harness to build. The dashboard picks a winner when the signal stabilizes.

dashboard.experiment({
  metric: "session_length",
  variants: ["layout_a", "layout_b"],
});

Per-player latency & reconnect telemetry

Why did Maya rage-quit? Her WiFi dropped at 13:42 — not your netcode. Per-player timelines with pre-diagnosed causes (NAT hairpin, relay fallback, carrier band switch) so you can tell a user problem from a you problem.