Overview
Test system-wide interface consistency and coordinated interactive state.
Capabilities tested
- complex state
- window management
- keyboard shortcuts
- persistence
- interaction architecture
Required outcome
A stable desktop workspace with multiple useful applications and persistent window state.
Requirements
functional
- Desktop and dock or taskbar
- Draggable and resizable windows
- Minimize, maximize, and close
- Search, notes, terminal, file explorer, and settings
- Themes and keyboard shortcuts
ux
- Clear window focus
- Usable small-screen fallback
- Accessible controls
technical
- Persistent window state
- Bounded window positions
- Production build must succeed
Constraints
Allowed
- Local persistence
- Fictional files and terminal output
- Established framework utilities
Forbidden
- Dead desktop controls
- Unbounded off-screen windows
- External desktop emulators
Acceptance criteria
- Windows can be moved, resized, focused, minimized, maximized, and closed
- Core apps perform meaningful local actions
- State survives a reload
- Keyboard shortcuts are discoverable and work
Evidence required
- Production build output
- Window interaction recording
- Reload persistence evidence
- Known-bug list
Exact prompt
prompts/challenges/browser-mini-os.md
# BuildArena Challenge Role: Senior frontend product engineer. Project: Browser Mini Operating System v1.0.0 Objective: Build a fictional browser desktop that demonstrates coherent, persistent multi-window interaction. Required outcome: Desktop, dock or taskbar, draggable and resizable windows, minimize/maximize/close, search, notes, terminal, file explorer, settings, themes, keyboard shortcuts, and persistent window state. Build order: Inspect the environment; build window focus and movement; prove resize/minimize/maximize/close; add useful applications; add persistence, themes, and shortcuts; run production validation. Verification: Run package scripts and verify a multi-window workflow, state after reload, keyboard shortcuts, narrow-screen behavior, and console output. Evidence to return: Commands, test results, interaction recording, known bugs, missing requirements, human intervention, final commit, and deployment URL only when authorized.