I build React products and mobile software that still has to work when the network doesn’t.
I’ve spent roughly seven years building frontend products, with React and TypeScript as the center of my work.
More recently, I’ve been working across React Native, Node, Express, PostgreSQL, testing, and releases to ship complete products.
Vicugna
The most substantial thing I’ve built recently.
An offline-first React Native application for agricultural and conservation field work.
People use it in places where connectivity is unreliable or absent. Work has to survive restarts, interrupted sessions, delayed synchronization, and conflicting revisions without asking field users to understand the machinery underneath.
Why it was difficult
Offline behavior shaped the local database, session model, synchronization strategy, and failure recovery from the beginning. It was not a feature that could be added after the happy path worked.
What I was responsible for
The React Native application, local persistence, synchronization and revision safeguards, backend integration, automated testing, real-device debugging, and release preparation.
Before Vicugna
My background is primarily frontend engineering: product interfaces, application state, component architecture, design implementation, and the less glamorous debugging work required to keep those systems dependable.
I’m still strongest on the frontend. The mobile and backend work is an expansion of that foundation, not a claim that every part of the stack represents seven years of equal depth.
Tika
A zero-dependency TypeScript library for deterministic SVG avatars.
Small API, stable output, and predictable browser and server behavior.
View the source →