For Windows users, the opportunity is less about replacing an established workstation than opening a project when that workstation is unavailable. But there is an important distinction between a convenient second editing environment and one ready to approve your next manufacturing run.
ZiroEDA brings KiCad projects into a browser
ZiroEDA describes its implementation as a TypeScript translation of KiCad’s C++ source, organized against the KiCad 10.0.6 codebase. Its repository lists schematic and PCB editors, interactive routing, electrical rules checking and design rules checking. It reads and writes native KiCad files rather than requiring conversion to a separate design format.
The documented GitHub workflow opens public projects read-only, with Save a copy available for creating an editable copy. The maintainers position the editor for small and medium designs, education and review; they recommend desktop KiCad for heavy projects and acknowledge that some dialogs and less-used tools remain unfinished.
That makes browser access promising for reviewing a board from another computer—but not evidence of complete desktop feature parity.
CNX Software’s Jean-Luc Aufranc opened the Olimex UEXT-CH390 schematic in Firefox, saved a copy, and opened its PCB layout to select components and traces. His smartphone attempts failed in both Firefox and Chrome. That establishes a limitation in his test, not a verified explanation of how the editor distinguishes phones from tablets.
The practical takeaway: browser-based editing is credible enough to explore, but a familiar toolbar is not a compatibility certificate.
KiCad Android takes the native-app route
Devesh Rai’s KiCad Android instead builds from upstream KiCad 10.99 sources. Its repository explicitly disclaims official affiliation and describes a keyboard-and-mouse-first application, with schematic and PCB editing, a push-and-shove router, Gerber viewing and command-line tools.
The project’s advertised capabilities include:
- A Vulkan-backed editing canvas.
- Integrated Freerouting autorouting.
- A STEP-capable 3D viewer through gl4es.
- Bundled KiCad 10.0.8 symbol and footprint libraries.
- An optional MCP server allowing Claude Code to inspect and modify designs.
These are maintainer-documented capabilities, not independent performance findings. Likewise, the developer’s reported matching Gerber and drill outputs against a macOS build are encouraging, but do not establish universal equivalence for every design.
CNX’s hands-on experience exposes the less glamorous part of desktop software on a small screen: clipped controls and awkward touch operation. Reducing Android’s display and font sizes improved usability. When direct GitHub loading unexpectedly requested credentials for a public project, downloading and extracting the repository ZIP allowed manual loading instead. CNX installed the APK from GitHub Releases and reported no Google Play distribution at the time of its test.
The lesson is straightforward: bring a keyboard and mouse, not heroic expectations for fingertip PCB routing.
Protect the desktop round trip
There is a compatibility detail worth checking before experimenting. The browser port’s 10.0.6 basis and the Android app’s 10.99 basis should not be treated as interchangeable version labels. Those are the respective projects’ stated source versions.
Official KiCad documentation says point releases preserve file compatibility, while major releases generally change formats. It also warns that files saved by a newer major version generally cannot be reopened by an older one, and explicitly recommends backing up designs before migration. That warning does not prove these ports will break a project; it explains why testing with your only copy is a poor experiment.
A prudent evaluation workflow is therefore:
- Duplicate the complete project before opening it in either port.
- Make a small, recognizable edit and save the result separately.
- Reopen that result in your intended desktop KiCad installation.
- Check the schematic, board, libraries and rule-check results before continuing.
- Review fabrication outputs before sending them to a manufacturer.
This is precautionary editorial guidance, not a claim that either project produces incorrect files.
Official KiCad continues to support maintained Windows, macOS and Linux environments; its documentation makes no equivalent guarantees for unsupported platforms. These unofficial efforts are best approached as additional ways into the KiCad ecosystem: potentially useful away from the desk, with the desktop workflow retained as the validation checkpoint.