Architecture Overview
MapleOS is organized like a desktop shell with app surfaces, windowing, shared file access, and stable deep links. Developer documentation here stays intentionally high-level: enough to build in the MapleOS style without overloading the page.
Desktop shell
The outer operating context for launching, arranging, and returning to programs.
Program surfaces
Apps are identified by stable IDs and opened inside consistent MapleOS chrome.
Windowing model
Users should be able to compare and combine apps side by side during real workflows.
Deep links
Links should move a user into the right program quickly without inventing a separate navigation system.
Principle for developers
A MapleOS app should feel like it belongs to the desktop before it tries to be clever. Users should understand where it lives, how to open it, and how it relates to the rest of the system.
If your app uses automation or AI, design those capabilities as visible layers inside the app model rather than hidden replacements for it.