- Status: active
- Goal: Advance
examples/mo_desktopfrom a runnable desktop simulation to a product-quality macOS-inspired UI: coherent system chrome, window behavior, controlled Finder/Safari/system surfaces, and reproducible Web plus macOS Skia presentation evidence, while preserving the shared app and thin-entrypoint boundary. - Non-goals: Reimplement every reference app, add framework controls, or claim new renderer/platform capability.
The desktop must no longer present fixed values as if they were live system
state. The shared app will use Program::new_with_environment, typed
Effect, and model-owned Subscription declarations. Web and macOS
entrypoints will inject the same host-service/timer/clock capability shape;
platform packages retain concrete browser/AppKit implementation details.
- Add a reusable Web
@services.TimerSource, driven by the existing browser event-loop clock, so Web can run the same long-lived subscription path as macOS. - Give timer frames meaningful monotonic
time_ms, and inject a wall-clock snapshot at the platform edge for the visible menu/lock/widget time. - Use typed
ServiceTaskeffects for appearance, file import, and external URL opening.AppEnvironmentstays in the Program closure; the business model stores only typed loading/result state, never host request ids or queues. - Replace string/index state with typed launcher/task messages, clamp control values, and prevent impossible no-window zoom/drag states.
- Make live clock/system status and real host-service outcomes visible in the UI; unsupported host capabilities must be presented as unavailable rather than as a fake successful system surface.
- The shared app provides a responsive lock screen and desktop shell.
- Finder, Safari, the app launcher, notifications, and Control Center have meaningful typed interactions.
- Light/dark appearance, Finder navigation/search/view mode, sliders, toggles, and window controls update through the model.
- Web wasm-gc and macOS Skia entrypoints remain thin runtime wiring.
- The live clock, system appearance, file import, and external-URL paths use typed Effects/Subscriptions with matching Web and macOS host adapters.
- Focused native tests, Web build, native entrypoint build, static validators, and browser screenshots pass.
The original implementation establishes the product shape. The remaining work is organized as vertical slices so visual polish and real interaction progress together rather than accumulating static mock surfaces.
- Capture current Web and native-Skia presentation baselines at desktop and compact sizes; record concrete interaction gaps before changing layout.
- Make desktop-window behavior feel native: coherent traffic-light semantics, maximized/compact geometry, predictable overlay dismissal, and focused regression coverage for each transition.
- Deepen Finder, Safari, launcher, Control Center, and Notification Center flows only where a model-owned interaction and a visible state change can be exercised end-to-end.
- Refine typography, translucency, spacing, focus/accessibility affordances,
and image-resource behavior against macOS reference captures without
introducing platform implementation dependencies into
app/. - Maintain native/wasm app tests, Web screenshot evidence, and macOS Skia build/real-renderer smoke evidence as each slice lands.
| Date | Decision |
|---|---|
| 2026-07-17 | Use a shared app package plus web_wasm and macos_skia entrypoints. |
| 2026-07-17 | Reproduce the reference's primary workflows rather than create non-functional stubs for every dock app. |
| 2026-07-17 | Use an image asset for the wallpaper and MoUI views/canvas composition for all desktop chrome. |
| Date | Note |
|---|---|
| 2026-07-17 | Reference lock screen, desktop, Finder, launcher, Control Center, dark mode, and Safari states captured and analyzed. |