Skip to dashboard

App Survival: Android Release Night M3 • TS + Vite

Mode: Select
Selected
None
-
Upgrades raise capacity & reliability. Repairs restore health. Both cost budget
Budget
$500
Rating
5.0 ★
Shift
0:00 / 9:00
Score
0
COMBO x1
System Health
Failures
0.0%
ANR Risk
0.0%
p95 Latency
0 ms
Coverage
78%
Target 70%+
Architecture
0
Battery
100
Android Internals
Time
0s
Jank
0%
Heap
64 MB
GC / OOM
0 ms / 0
Seed
Active: 0
Reset uses the seed above (if set).
Challenges
Daily: -
Weekly: -

        
Achievements
Preset: SENIOR • Unlocked: 0/0
Trust & accessibility
A11y: 100/100 • Privacy: 100/100 • Security: 100/100 • Support load: 0/100
CoverageGate and enforcement weight
Drag components to rearrange. Link mode: click source → click destination
Backlog
Capacity 0/0 +0/min
Fix tickets or defer
Refactor Roadmap
Suggested sequence to pay down architecture debt (Staff/Principal-style).
No roadmap yet.
Platform
Latest API 0 • Min API 0
Old devices 0% • Low RAM 0%
Regions
Reg pressure 0
Compliance and rollout gates
User votes (live sentiment)
Perf: 0 • Reliability: 0 • Privacy: 0 • A11y: 0 • Battery: 0
No reviews yet.
Incidents
No incidents… yet.
Postmortem
No run yet.
Scoreboard (local)
⚠ Tampered
Top runs stored in localStorage.
No scores yet.
Android realism features (implemented)
  1. FrameGuard frame budget and jank meter (16ms model)
  2. MainThreadGuard IO on main strictness (adds ANR and jank)
  3. HeapWatch heap meter with GC pauses and OOM crashes

Recommended starter graph: UI → VM → Domain → Repo → (Cache → DB) and Repo → Net. Add Observability + Feature Flags to reduce blast radius

Incident
-
Respond fast: fix or defer the top ticket to stop the bleed.

Welcome to App Survival

You are the on-call engineer for an Android app on release night. Keep the app alive by managing architecture, fixing incidents, and balancing competing pressures.

  1. Place components (UI, Network, Database...) on the canvas
  2. Link them together to form your architecture
  3. Press Start and respond to incidents as they arise
  4. Survive the shift with a good rating and low debt
Full guide: GAMEPLAY.md

Run Complete

Final Score
0
Rating
-
Duration
-
Debt
-
Tickets
-

Profile

Preset
Unlocked: 0/0 • Best survival: 0s
Hidden achievements show up as “Hidden achievement” until you unlock them.

Settings

Refactor options

Target
Refactors spend budget and reduce architecture debt. Pick the cheapest thing that fixes the worst violation.