Native macOS · Systems engineering
Motion Control, Rebuilt
An AI-assisted modernization of a legacy stage-rigging application into a modular Swift and SwiftUI macOS prototype, with a drive simulator and verification against the original C implementation.
The problem
The original 32-bit application could no longer run on modern macOS. Its behavior had to be understood from the source before a credible replacement could be designed.
How I approached it
I directed the migration, set product and safety decisions, tested builds by hand, and used independent reviews to challenge generated code and documentation. An audited specification anchors the rebuild; the original C code acts as a reference for numeric behavior.
Inside the build
- Replaced an i386-only Objective-C/C architecture with 11 modules targeting modern macOS.
- Compared unit conversion, target clamping, and speed behavior against 1,400 generated legacy reference cases.
- Used strict concurrency and regression tests to address stale input, stop handling, and shutdown races.
- Built a simulator-only demo whose packaging checks refuse hardware-control symbols.
The result
Produced a simulator-only macOS demo with a modular motion engine, SwiftUI console, and regression coverage for reproduced concurrency failures. The app’s module boundaries keep hardware access out of the demo binary.
Where it stands
Verified in simulation and loop-back only. The software has not driven real hardware, is not safety-certified, and requires bench validation before hardware motion can be enabled. Client identity is omitted.