Firmware, field tools, and the software around them.
Flipper Zero · RF / NFC · iPhone / macOS · release automation
I work at the seam between a physical device and the person using it: the firmware on the Flipper, the companion app on the phone, the macOS bench, and the package pipeline that makes updates trustworthy.
| Layer | What I actually build |
|---|---|
| Hardware | Flipper Zero, Module One, C1101 and small embedded controllers |
| Protocols | NFC, Sub-GHz, BLE, USB and the edge cases between them |
| Apple tools | Native iOS and macOS apps for control, files, diagnostics and field work |
| Operations | Independent packages, protected-app audits, reproducible releases and routing failsafes |
SYSTEMS C · C++ · CMake · Make
APPLE Swift · SwiftUI · native iOS/macOS
AUTOMATION Python · Shell · jq
DEVICE I/O JavaScript · TypeScript · BLE · USB
- Tumoflip — my independent Flipper Zero firmware: custom desktop, ARF / ProtoPirate, NFC, Sub-GHz, Module One and the BLE App Bridge.
- TumoCompanion — the iPhone control room for firmware, FAPs, files, screen control and field workflows.
- Tumoflip Studio — the macOS workbench for Flipper Zero, Tumoflip and Module One.
- FW Packages — an independent package catalog with immutable releases and protected-app audit lineage.
t-vgm-fw · Disk Ray · FlipperRelay · Shadowrocket configs · rf-macro-sim
- A device should behave like its UI says it will.
- A package should be independently verifiable, not tied to a convenient label.
- A green CI run is useful; a real device test is the final word.
From raw signal to verified release — one small, stubborn system at a time.


