I build the systems
underneath the app —
not just the app.
I'm the Founder of Sonora Media Labs. I design and ship full-stack products end to end — engines in Rust, interfaces in Flutter — across networking, audio, auth, data pipelines, and game systems.
rScout
activeA Rust network scanner with multi-source device fingerprinting — SSDP/UPnP, mDNS, MAC OUI, and DHCP hostnames — to identify devices like Echo, Apple, Samsung, and Xiaomi hardware even through MAC randomization. Runs through a custom split-pane terminal UI.
Tunes4R
activeA cross-platform audio player for Android, Android Automotive, iOS, and macOS. Rust playback core built on Symphonia handles seeking and streaming over HTTP range requests; Flutter drives the interface, lyrics sync, and now-playing UI.
UILand
frameworkA UI framework written in Rust, built around a Visual Snapshot Protocol that lets AI agents validate widgets directly, plus a theming and chrome-template system for building consistent app interfaces.
UserBrew
platformAn identity and access management platform in hexagonal architecture, spanning roughly 33 crates. Supports RBAC, ABAC, ReBAC, and ACL policy models, with a React admin console on top.
FlowForge
platformA data pipeline and workflow orchestration engine, with a Connector/DataLink architecture for wiring sources and destinations, visualized and edited through a ReactFlow-based canvas.
CrabCraft
activeA Minecraft-style voxel engine built from scratch in Rust — greedy meshing, warped-noise terrain generation, infinite streaming chunks, AABB player physics, ore veins, and cave systems.
fingerid
libraryAn audio fingerprinting library using Shazam-style spectrogram peak hashing, built for fast, accurate matching between short clips and full-length tracks.
rustdata
libraryA Spring Data–style ORM for Rust, generating multi-dialect SQL from proc macros so data access code stays declarative across database engines.
Most of these products share the same instinct: build the engine first, get the boundaries right, then let the interface follow. That shows up as playback cores that survive a bad network, permission systems that model real organizational structure, and terminal UIs that don't corrupt the buffer when you resize them.
It also means leaning on AI agents heavily during development — and stepping in personally when an agent gets stuck, misdiagnoses a bug, or needs a second opinion grounded in twenty years of shipping systems that had to actually run in production.
Want something built that actually holds up under real conditions?
Available for systems architecture work, technical advisory, and full-stack builds where the hard part is underneath the UI.