Figma explains structure, but it struggles with behavior. I prototype on device to understand pacing, resistance, timing, and to save engineering time. For the things you only feel when the app compiled.
Continue readingThe language we use in meetings shapes what we build. Call it a "list," and you get a list. Call it "collaboration," and you might build a system.
Continue reading
I built a stopwatch to understand the constraints of time. It forced trade-offs on precision, trust, and platform limits that most apps ignore.
Continue readingI pushed back on forking repositories on GitHub Mobile. I thought it was too complex. Users proved me wrong, and that changed how I evaluate feature requests.
Continue readingNotifications are usually noise. We designed a system that reduces that noise without breaking trust. Most of the work was in the edge cases.
Continue readingShutting down a beloved product for millions of users is mostly a trust problem. The goal wasn't just simple migration into the new app, it was making sure people felt their data and history were treated with respect.
Continue readingCode review is heavy work. I worked with engineering to break it into smaller, mobile-first steps without losing the context that makes reviews safe.
Continue readingI focus on productivity tools, complex systems, and native platforms. I'm at my best where judgment matters and quality has to last.
Staff-level scope. Productivity-focused. Remote-first in Germany or EU / EST time zones.