Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/shadownrx/windows/llms.txt

Use this file to discover all available pages before exploring further.

NEX OS is a next-generation computing experience built entirely for the web. It is not a UI clone or a cosmetic imitation — it is a fully engineered operating system ecosystem that runs inside any modern browser. Built on React 19, TypeScript, AssemblyScript (WASM), and Three.js, NEX OS delivers a complete OS lifecycle from UEFI boot through login to a fully interactive desktop, complete with a virtual file system, a multi-window manager, neon visual themes, and over 20 built-in applications — all without installing a single native binary.

Quickstart

Clone the repo, install dependencies, and boot NEX OS locally in under five minutes.

Architecture Overview

Deep dive into the provider tree, OS state machine, and micro-frontend model.

Apps Overview

Explore all 24 built-in applications — from NexBrowser Pro to the WASM Task Manager.

useWindowManager API

Full reference for the central window lifecycle hook used across every app.

​
What Makes NEX OS Different

Most browser-based “desktop” projects render a static layout with draggable boxes. NEX OS goes several layers deeper. Every application runs in its own isolated context under a central WindowManagerProvider orchestrator — a micro-frontend architecture where windows carry their own state, z-index memory, snap position, and saved size across minimize/restore cycles. The OS itself runs through a deterministic state machine (OFF → BOOTING → WINDOWS_BOOT → LOGIN → DESKTOP → SHUTTING_DOWN → RESTARTING) rendered entirely in React, with each phase producing a distinct visual screen.

​
Key Features

Window Manager

Full window lifecycle: open, close, minimize, maximize, snap to halves and quadrants (Windows 11 style), multi-desktop virtual workspaces, and keyboard shortcuts (Win+D, Win+Tab, Alt+F4).

Virtual File System

In-memory file system managed by FileSystemContext — create, read, update, and delete files and folders recursively, with drag-and-drop support in File Explorer and .nex executable support.

NEX Runtime

An interactive simulated runtime engine that lets you install virtual packages, run scripts, and execute virtual .nex binaries from the integrated CMD and Bash terminals.

WASM Performance Layer

Performance-critical logic (Task Manager CPU/RAM monitoring) is compiled from AssemblyScript to WebAssembly via assembly/index.ts, with a JavaScript fallback managed by the useWasmEngine hook.

Neon Themes

Three dynamic neon visual themes — Cyberpunk, Matrix, and Synthwave — each with reactive 3D backgrounds powered by Three.js / @react-three/fiber that respond to the selected theme in real time.

PWA Support

Installable as a native-like app on any device via vite-plugin-pwa, with offline resource caching and full PWA manifest support baked into the production build.

Complete OS Lifecycle

Experience the full boot sequence: UEFI OS selector → POST/BIOS animation → Windows boot splash → Login screen → Desktop → Suspend → Shutdown → Restart — all rendered in-browser.

24+ Built-in Applications

From a full-featured Notepad 2.0 and Paint canvas to a Spotify-style music player, VS Code editor, NexBrowser Pro, and a real-time WASM-powered Task Manager.

​
Tech Stack

NEX OS is assembled from a carefully chosen set of modern web technologies, each serving a specific engineering purpose.
TechnologyVersionPurpose
React19.xBase UI library with concurrent rendering
TypeScript~5.9Strict typing across the entire codebase
Vite8.xNext-generation bundler with instant HMR
Tailwind CSS3.xUtility-first styling and design tokens
Framer Motion12.xFluid animations and window transitions
Three.js / R3F0.183GPU-accelerated 3D dynamic backgrounds
AssemblyScript0.28Compiles to WASM for intensive computation
Rust—Secondary WASM engine (wasm-engine/) for system utilities
@fluentui/react-icons2.xFluent Design system iconography
vite-plugin-pwa1.xPWA manifest, service worker, and offline cache

​
System Architecture at a Glance

The entire application is rooted in a layered provider tree defined in App.tsx. Context providers are nested in a strict order so that inner providers can consume the state of outer ones. 
App.tsx
├── SettingsProvider        ← User preferences (theme, volume, wallpaper…)
│   └── MusicPlayerProvider
│       └── FileSystemProvider      ← Virtual file system
│           └── NexRuntimeProvider  ← NEX package runtime
│               └── DesktopProvider ← Desktop icons + virtual desktops
│                   └── UIProvider  ← Start Menu, Widgets, Switcher visibility
│                       └── WindowManagerProvider  ← Window lifecycle core
│                           └── AppContent  ← OS state machine
│                               ├── OffScreen / BootScreen / WindowsBoot / UEFI
│                               ├── LoginScreen
│                               └── Desktop (Windows) | NexDesktop (NEX OS)
│                                   ├── Background3D
│                                   ├── Window × N
│                                   ├── Taskbar
│                                   ├── StartMenu
│                                   └── Overlays (ContextMenu, TaskView, Widgets…)
Data flows unidirectionally: user interactions trigger component event handlers, which call context hooks (useWindowManager, useSettings, etc.), which update context state and cause targeted re-renders.
NEX OS is a technical demonstration of modern frontend engineering capabilities. It is not affiliated with, endorsed by, or connected to Microsoft Corporation or Spotify AB in any way. All simulated product interfaces are for illustrative purposes only.

Build docs developers (and LLMs) love

Get started for freeTalk to us