I’m embarking on an ambitious project to launch a pair of operating systems — one for mobile devices and one for desktop / laptop computers. I deliberately chose Both platforms because I need a seamless experience across phones, tablets, and traditional PCs, without depending on Android, iOS, Windows, macOS, or any other pre-existing stack. The mobile side will be entirely Custom, so we’re starting from a clean slate and can define the kernel, UI layer, and security model exactly as we want. Here’s the flow I have in mind. First, we’ll specify hardware targets and draft the architecture (kernel type, driver model, boot process). Next comes a minimal viable OS for each platform: the desktop build must boot, recognise core peripherals (storage, networking, display), and expose a simple window system; the mobile build must initialise on selected ARM boards, offer touch input, radio management, and a lightweight launcher. Once that baseline is stable we can iterate on power management, package management, and developer tooling. Deliverables (milestone-driven) • Technical architecture documents for both kernels • Bootable ISO/IMG images for x86-64 / ARM64 test hardware • Source repository with build scripts and cross-compilers • Minimal GUI shell for desktop, touch launcher for mobile • Basic SDK: compiler toolchain, emulator, and documentation I already have funding allocated and will handle certification costs; what I need is deep expertise in C/C++, Rust or similar systems languages, low-level debugging, and familiarity with u-boot/UEFI, Wayland or comparable display servers, and embedded drivers. If this sounds like your kind of challenge, tell me which part of the stack you’d tackle first and the tooling you prefer.