Overview
Otto OS is a native Windows 11 shell surface inspired by the spatial language of macOS. It adds a notch-style top bar, a Dynamic Island-style expanded surface, a floating Dock, and custom window controls. I built it as a Rust workspace with one main constraint: native Windows integration should not leak into layout, state, or rendering code.
Crate boundaries
The workspace separates pure behaviour from native effects. otto-core holds the models, layout, hit testing, formatting, motion rules, menu rows, and theme resolution. otto-platform owns Win32, shell, media, audio, display, taskbar, and app-bar calls. otto-render owns Direct2D, DirectWrite, GDI, and layered-window presentation. otto-os coordinates windows, messages, timers, and feature state.
Dependencies point one way: otto-os depends on otto-render and otto-platform, and both depend on otto-core. This keeps the geometry rules testable through cargo test --workspace without relying on a live shell.
Recovery and cleanup
Changing the taskbar or app-bar work area is a side effect that outlives the process if it is not undone. Otto OS keeps crash-safe recovery state in shell_recovery.json, provides --restore-shell to repair it, and provides --quit so upgrades and uninstalls can close the shell cleanly. Owned native and graphics resources are released explicitly rather than left to process exit.
Native acceptance
Unit tests do not prove what a user sees on a desktop. The native runner launches a separate Otto process for each scenario, drives real Win32 input, checks visible surface topology and geometry, waits for visual stability, and stores screenshots and a report under artifacts/e2e. The scenario set covers success, fullscreen, Genie minimize, Dock, keyboard navigation, and stall handling, plus standalone recovery, appearance, and audio checks. A non-zero exit is treated as a release-gate failure.
Release
Version 1.0.0 is dated 2026-11-21 and ships through GitHub Releases as a per-user installer, a portable ZIP, SHA-256 checksums, and WinGet manifests. A Windows SDK MSIX lane exists for the Store path. Without a publisher certificate, that lane produces an unsigned package for local inspection only.
Limits
Capture fidelity, DWM cloak timing, frame pacing, DPI behaviour, and visual continuity still require acceptance runs on real Windows 11 desktops; the automated suite does not replace them. The MSIX lane needs a Store identity and a publisher certificate supplied at build time, and the repository does not contain either.