LinPad OS: designing a Linux desktop for the iPad

What is LinPad OS?

LinPad OS is a free, open-source project that runs an Alpine Linux environment on the iPad itself. It lives inside an iPad app; it does not replace iPadOS. The desktop provides windows, tiling and workspaces, with Linux applications such as Firefox, VS Code, Thunar and VLC. A terminal adds tools including git, Node and Python.

The work builds on iSH-ARM64, combines an emulator with a SwiftUI desktop shell, and connects Linux applications through a Wayland bridge. That stack matters to an engineer. For a person opening the app, the important questions are more immediate: can I find my files, open the right tool, type into it and keep what I make?

LinPad is our founder’s own project, shared publicly under GPLv3. It is a prerelease, rather than a finished client delivery or an App Store launch. The lessons below come from that active development work.

A desktop has three kinds of input to get right

A conventional desktop can assume a mouse and keyboard. An iPad cannot. Someone may use a keyboard and trackpad for an hour, detach them to use touch, then bring up the on-screen keyboard inside a Linux app. The interface has to keep working through those changes.

That affects window controls, menus, focus and shortcuts. A resize edge that works with a pointer can be frustrating with a finger. A shortcut is useful only if the correct window receives it. A panel must stay clear of the dock and the keyboard. These are product decisions expressed through software, not decoration applied after the build.

• Give common actions a visible route as well as a keyboard shortcut.
• Make open, focus, minimise and restore behave consistently.
• Check menus and window controls with touch as well as a pointer.
• Test typing and focus inside the actual Linux applications, not only in the desktop shell.

Make Linux software discoverable

A package manager is a strong foundation, but a command prompt is a poor introduction for someone who does not yet know what to install. The LinPad Store gives the Alpine application catalogue a browsable interface, with curated packs that group tools around useful tasks.

That is the same problem we see in a web product with powerful features and weak navigation. The implementation can be capable while the person using it has no clear next action. Better grouping, plain labels and useful defaults reduce the amount of knowledge a newcomer must bring.

Developer tools provide a concrete example. A Linux terminal, an editor and a browser are individually useful. Presenting them as a coherent workflow makes the product easier to understand: work on code, inspect files, read documentation and return to the terminal without leaving the local environment.

Personalisation should reach the applications

LinPad supports desktop styles, colour palettes, icon packs and wallpapers. The theme work extends into the Linux applications, rather than stopping at a coloured panel around them. The era demos show recognisable desktop ideas, from Classic 98 and Luna to Aero and a monochrome Dot Matrix style.

The interesting design challenge is consistency. Switching appearance should not force someone to relearn the underlying behaviour. Windows still need clear focus states; menus still need legible text; keyboard shortcuts still need to work. A coherent design system gives those behaviours a stable home while allowing the visual treatment to change.

For a website or SaaS interface, the same principle applies to branding, dark mode and responsive layouts. Colours and typography are only part of the system. States, spacing, interaction patterns and readable content have to stay coherent too.

Reliability belongs in the user experience

An iPad app can be suspended or terminated when memory runs short. Browsers and code editors are demanding workloads. A beautiful desktop loses its value quickly if someone cannot return to their files or understand how to recover after a problem.

LinPad’s engineering includes memory policy, session restoration, autosave defaults, backup and restore, diagnostics, repair tools and an update path with rollback. These features are less visible in a promotional clip, but they shape whether a person can trust the product.

The web equivalent is familiar: forms that preserve input, clear errors, recoverable edits and predictable loading states. We treat those details as part of design because they determine what happens when real use departs from the ideal demo.

Show the product, explain the constraints

The video above includes actual iPad footage. The longer personal article also includes developer and desktop-theme demos made with simulator footage, labelled as such. Keeping those sources clear helps a reader understand what the demonstration establishes.

The same care applies to performance. LinPad’s native ARM64 JIT is its fast path and requires StikDebug setup. A slower compatibility mode is available without JIT. Measurements from the Mac emulator or simulator cannot be passed off as results for every iPad.

LinPad targets M1 or newer iPads with iPadOS 17 or later. It requires sideloading with your own Apple ID. Heavy apps depend on available memory, and Docker, Steam and x86 games are outside the supported scope. A useful product page makes those requirements easy to find before someone invests time in installation.

What founders can take from LinPad

Start with the job a person wants to do. In this project, that job is to use local Linux tools on an iPad. Then make the route into the product clear: prerequisites, installation, a useful first session and a way to recover. The interface and the engineering have to support the same promise.

Whether we are building a business website, a SaaS dashboard or a native application, the work is similar in one respect: the person using it should not have to understand the implementation to make a good next decision. Demonstrations should show real behaviour. Documentation should answer the awkward questions. Navigation should make capability visible.

If you are planning a product with several user roles, complex tools or an unfamiliar workflow, bring that problem into the design brief. A feature list alone will not tell the team which decisions the interface needs to help people make.

LinPad OS: common questions

The installation guide and source repository are the references for the latest prerelease requirements.