Browser platform of short scenario games

Shiftworks

Created by Ishan Bangroo Tactical browser games about overload, prioritization, interruption recovery and cleaner handoffs

Shiftworks is a series of short browser modules about staying usable under pressure. Across the games, the same practical moves recur in different forms: spot the live signal, protect working room, leave a clean next step, and stop every loud thing from passing as urgent. The tone is grounded and meant to survive a real phone screen.

Diverse audience Mobile-friendly play Bounded AI debrief in one module Short runs No install needed Touch and keyboard support
What the platform is for

Practicing overload management in ways that stay readable under stress: signal triage, interruption recovery, return-point notes, capacity-aware help seeking, handoffs, and small reset moves that make the next action workable.

Why the modules change shape

One genre never fits everybody. Shiftworks carries the same practical habits across a district map, a communications module, a planning board, a neon courier runner, and a dispatch network so structure changes while the core moves stay recognizable.

How the platform plays

Each module stands alone. Taken together, they behave like a platform rather than one-off demos: movement, comms, planning, handoffs, and rapid filtering all get their own form.

Best first run
If you want the easiest phone game first, start with Breakwater Watch. You only need to drag 3 sliders: one to Dock now, one to Wait outside, and one to Ignore.
Module 1 · Top-down action adventure

Harbor of Drift

Fight through the harbor in a top-down shooter, restore relays, sort urgent from loud, and keep the district from turning every interruption into the only thing that matters.

Main feelTop-down shooter
Core skillCalm action under pressure
Session7 to 10 minutes
ControlsTouch + keyboard
Module 2 · Narrative communications game

Kindline Switchboard

Pick the line that actually deserves the board, route the exchange with one bounded response card, and leave a backup note strong enough for the next interruption.

Main feelQuiet narrative pressure
Core skillInterruption recovery
VoiceOptional Quayline readout
Session5 to 7 minutes
Module 3 · Planning board

Ward Relay

Sort incoming work into now, next, and noise, make one board action per round, and leave a handoff that the next person can actually use.

Main feelTurn-based sorting
Core skillTask choreography
Handoff qualityVisible
Session6 to 8 minutes
Module 4 · Mobile action runner

Emberline

Run with 3 boxes. Jump crates, slide under low bars, clear pink fake alerts, and use short slow-down moments when the screen gets too busy.

Main feelSide-scrolling courier action
Core skillFocus under pressure
ControlsPhone + desktop
Session5 to 8 minutes
Module 5 · Slider-based harbor watch

Breakwater Watch

Drag 3 sliders each round. Send one signal to Dock now, one to Wait outside, and one to Ignore. Keep the harbor calm by not treating every ping like an emergency.

Main feelSimple slider board
Core skillUrgency filtering
Main moveDrag 3 sliders
Session4 to 6 minutes
Recurring moves across the platform

Different genres, same operational backbone

Signal triage
Not every loud thing deserves motion. Several modules ask what is now, what is next, and what is noise.
Return-point notes
When work cannot finish cleanly, the platform rewards leaving the next step readable instead of hiding it.
Short recovery windows
Small reset moves matter more here than fake heroic overreach.
Capacity-aware help seeking
Backup is framed as operational judgment, not failure.
Scenario
The platform aims for vivid and playable scenarios.
Recommended first run: Breakwater Watch first if you want the clearest phone-friendly game, then Harbor of Drift for action.
Deployment: Static files in public/ and the Quayline function in functions/api/.