About
I'm Haris Muntazir. Bytefy is my studio, and the name is the idea: start at the byte and keep going until the thing ships.
What I do
I work at every layer I can reach. I build Android itself for the phone I carry, write the apps that run on it, and put the products behind them on Cloudflare's edge, where there is no server to patch.
Most of what I build starts as a frustration: banking apps that won't open on a custom ROM, notes that pile up in lists, screen-time limits that are easy to skip, trees measured by eye. I plan before I code, write the rules down, and keep the rules when the code changes.
AOSP & Kernel
Android 16 on Dimensity 1080 (MT6877). Custom Clang toolchain, device trees, and hardware abstraction layer (HAL) bring-up.
Attention & AR
Flutter, Kotlin, ARCore 3D raycasting, 50m GPS geofencing, and zero-button rotary dialer gestures.
Zero-Ops Scale
Cloudflare Workers, D1 distributed SQL, R2 object storage, Workflows, and headless Browser Rendering.
Formal Invariants
Double-entry ledgers, Hoppus geometry, 100% verified contracts, and zero mock data in production.
Engineering Areas
9 verified projects across 5 specialties
Systems
Android from the device tree up.
Measurement & AR
Exact formulas in tools people pay for.
Serverless
Products with no server to patch.
Gestures
Interfaces with zero buttons.
Rules I keep
The principles that govern every Bytefy codebase, from kernel compile to edge worker.
Zero mock data
Every number on this site is measured, read from a repo or written in a design rule.
No server to patch
If it can run on Workers, D1 and R2, it does.
Physics over decoration
Interfaces should feel mechanical: inertia, snapping, lingering, not blinking.
Small modules, strict contracts
Plans before code, invariants written down, and nothing silently removed.