A manifesto on Design Engineering.
Bring designers and engineers together earlier, prototype to learn, build systems and tooling that scale, and treat code as a design material.
Fewer handoffs and better products. Let’s build the future that actually ships.
I’ve been refining KK Sans again: rebuilding the lowercase a, fixing joins in heavier weights, adjusting spacing, and giving the figures some overdue attention.
A curve can be technically smooth and still look wrong. A measured gap can still make a word feel uneven.
Link below.
Open a panel, close it, then immediately open it again. Does it stay open?
It sounds ridiculous, but a delayed cleanup can let an old decision hide it after the newer one says otherwise.
A small web example, with the accessibility bits too. Link below.
I don’t post much, but this felt worth unfolding :)
For the past year, I’ve helped shape the core software experience for iPhone Duo, especially multitasking.
A lot of it came down to tiny decisions, the kind that, when they’re right, just disappear into how the product feels
Prototyping in code isn’t about shipping that code straight to production.
It’s about capturing the design intent as clearly as possible so you can then figure out how to make it production-ready.
