Blog

The entry screen in Patterns went through four complete rewrites. What each one got wrong and what the process taught me about design decisions I thought were resolved.

The WatchKit experience building Steepr's watch app. What extreme constraints teach you that abundant screen space hides.

The micro-decisions that separate an app that feels polished from one that feels assembled. Specific examples from my own work.

The exact thought process behind pricing my App Store apps. What I looked at, what I ignored, and what I'd do differently.

The philosophy behind running your own infrastructure, the real costs involved, and an honest look at when it stops making sense.

Not a sponsored list. Just what I've ended up with after trying a lot of things, and why each one is still here.

Going deep on native platform constraints taught me things about UI architecture that cross-platform abstractions kept hidden. Here's what transferred.

Exploring the hybrid role of the Design Engineer and why the gap between design and development is shrinking.

Why mobile-first is no longer just a trend, but a necessity for modern full-stack development.

How to maintain design and logic consistency across web and mobile platforms using the modern JS ecosystem.

Why speed is not just a technical metric, but a fundamental pillar of great user experience design.

How to use motion to guide users, provide feedback, and add a layer of polish to your applications.

How to strip away the noise and build focused, effective software for the modern user.

How a robust design system acts as the ultimate multiplier for speed and consistency in full-stack development.

A small habit that saved me from a recurring problem. Typography decisions that look right in a design file can fall apart completely in code.

How AI is changing the way we design and build interfaces, and why the human element is more important than ever.

Why the best APIs and developer tools are the ones that feel like they were designed for humans.

Why typography is 90% of design and how to master it as a full-stack developer.

Being the designer and the engineer on the same product doesn't automatically mean the two sides talk to each other. Here's what I had to unlearn.

None of my apps started with market research. Here's why I think that's actually a reasonable way to work, and what it costs.

The story of building Steepr, my first native iOS app. Why readiness is something you feel after shipping, never before.

Five apps in the App Store sounds like a milestone. Looking back, each one taught me something different about why finishing is harder than building.