What should an Africa-first operating system decide for its users?

Why interesting

Omarchy shipped Arch with tuned defaults and a written doctrine, then passed 1.18 million ISO downloads in year one. The formula is curation plus doctrine over an existing base. That base assumes fast always-on internet, stable power, recent hardware, and cloud AI priced for Western wallets. None of those hold where the builders we most want to reach actually live. The hardest conditions should drive the design, not decorate the marketing.

Context

Second-hand refurb machines are the personal-computing reality across much of Africa. Connectivity is intermittent and metered. Power outages are routine, and cloud AI costs hard currency. An OS that treats these as first-class constraints (offline installs and updates, potato PCs as a primary target, a local model as the default agent) serves a population the incumbent setups structurally cannot prioritize.

Hypotheses

• Offline-first install and update paths materially widen who can adopt a serious dev OS
• A small local model as default agent is an economic unlock, not a convenience
• Hard conditions (power, bandwidth, old hardware) produce better systems engineering, not worse

Experiment ideas

• Daily-drive Omarchy for a month; journal every papercut the African-constraint lens catches
• Attempt a full offline install path from a hand-to-hand USB image
• Measure a local-model agent's usefulness on a 2013-era laptop with 4GB RAM

Needed knowledge

• Arch packaging
• Hyprland/Quickshell config
• offline delta updates
• local LLM serving

Linked Builds

No linked Builds yet.