From writing assembly to tuning Android kernels, I've always cared about the layer most people never see — the one that makes everything else feel right. Now I'm building my first mobile game.
Every layer of the stack has taught me something. Here's the arc.
Started with Assembler and C++, building a ground-up understanding of how software actually works. Java followed — object-oriented thinking added structure to instinct.
Developed and sold UI themes on the Magmic marketplace for the BlackBerry platform — an early introduction to shipping real products to real users and caring deeply about how something looks and feels.
When the first Samsung Galaxy launched, dove into custom kernel and ROM development — stripping out bloat, compressing images, and tuning every layer for performance and stability. The belief that software should get out of your way stuck.
Picked up Python for scripting, automation, and light tooling. A practical language for getting things done quickly — which, after years of C++ and assembly, feels almost like cheating.
Years at the low level taught me to reason about the whole, not just the surface.
From BlackBerry themes to Android ROMs — the experience has always mattered as much as the code.
Mobile is personal. Every tap, transition, and frame rate is a conversation with the user.
Every interaction considered. Every detail deliberate. Something worth your time is on its way.
Designed from scratch to challenge and reward in equal measure. No filler, no padding.
Built by someone who has lived inside mobile platforms. It will feel like it belongs on your phone.
Same philosophy that drove the ROM work — strip everything that doesn't need to be there.