Custom AOSP, embedded Android, and Unity integration.
I take on the low-level Android work most app shops won't: adapting a custom AOSP image to your board, getting a real-time hardware sensor into a Unity scene, or building the app that ties a device together. If your product is Android running on hardware you designed, this is the work I do, as an independent AOSP consultant.
BACKGROUND Before embedded Android I spent ten years as an IBM mainframe systems programmer, working close to the metal, where a change ships only after it's understood, then close to a decade building large-scale data infrastructure, including at a FAANG company. That's the reliability culture and systems depth I bring to custom AOSP and firmware-adjacent work.
What I take on
Custom AOSP for RK3588 boards
Adjusting and building custom Android images for RK3588 single-board computers: kernel and device-tree changes to get a board booting your software reliably. The vendor flow leans on Windows and manual steps; I've flashed these from a Linux host and scripted the process end to end, so the feedback loop is actually workable.
Unity ↔ Android / hardware integration
Wiring Unity to the Android layer and to real hardware (sensors, GPIO, peripherals) for simulators, kiosks, and interactive installations. This is the glue between a Unity experience and the device it runs on: reading a board's GPIO pins so a physical control drives the game, or getting live sensor data into the scene fast enough to be usable.
Data engineering
Large-scale data infrastructure: the work I did for close to a decade before embedded Android, and still take on. Batch and streaming pipelines, ETL platforms, and the shared tooling other teams build on: Spark, Kafka, Airflow, and the cloud data stack.
Android app development
Android apps in Kotlin or Flutter, including BLE and sensor work: talking to hardware over Bluetooth Low Energy, reading sensors, and handling the on-device data. The two local-first apps on this site are Flutter builds; the embedded work below is Kotlin and native.
Field notes
Not a portfolio pitch, but actual write-ups from the work. These come out of my work as software engineering tech lead at Strikeco, on a commercial tennis-simulator device built on custom AOSP hardware with Unity integration.
If that's the shape of your problem (custom Android on your own hardware), tell me what you're building and where it's stuck. No forms, no calendar bookings; just email me directly.