Interactive demo · BLE device × mobile app × cloud

The happy path is the easy part.

One green line from power-on to first value, and 68 red branches across 4 journey lines trying to pull your users off it. Good architecture turns dead ends into detours.

Version v1.0 · Newsletter & updates
1
happy path
unhappy branches on this line alone

Good architecture turns dead ends into detours.

Unlock the full map: scenarios, Problem/Solution, and the manager view.

VIEW
WITHOUT ARCHITECTURE
· Get your readiness score
JOURNEY LINES

Pick a scenario

GLOBAL HAZARDS: CAN STRIKE AT ANY STATION

What the unhappy paths cost

Same catalogue, translated into a funnel. Flip Problem/Solution above and watch the numbers move. v1 covers the onboarding line only: the operation loop needs a per-cycle model (v2).

WHERE THE NUMBERS COME FROM
ACTIVATION RATE
TICKETS PER USER
WHY MORE TICKETS THAN USERS
ILLUSTRATIVE PRESET
ACTIVATION RATE
without → with architecture
SUPPORT TICKETS / COHORT
ticket events, without → with: one user can file several
WHAT GOOD ARCHITECTURE IS WORTH
ONBOARDING FUNNEL ·

All probabilities are illustrative presets derived from likelihood buckets (common 15% · occasional 5% · rare 1%; recovery 5% without vs 90% with architecture; 60% of dead ends file a ticket): not real statistics. Replace with your telemetry.

WHAT IS HAPPENING?
WHY DOES IT MATTER?
WITHOUT PROPER ARCHITECTURE
HOW THE SOLUTION WORKS
MANAGER TAKEAWAY
Pick a scenario above, click any red branch on the map, or use arrow keys on the map to explore station by station.

The prototype works when everything goes right. The product succeeds when it handles what goes wrong.

Next step

How many of these branches can your product survive?

Before writing more code, identify the decisions that prevent expensive rewrites: connection states, sync rules, update strategy, recovery paths.

Identify your launch risks