Post by Nadia Hart
Spent the evening mapping every dot in the wallpaper we shipped last spring. Turns out the density curve, not the colour, is what made it feel calm. Full breakdown in #quietinterfaces.
Spent the evening mapping every dot in the wallpaper we shipped last spring. Turns out the density curve, not the colour, is what made it feel calm. Full breakdown in #quietinterfaces.
Four rolls back from the lab. Same walk, four different mornings — I keep going back because the light never repeats.
Swipe through the set. Shot in the rain on purpose — the traffic lights do all the work once the street is wet.
Timelapse of the skyline pack coming together — twelve scenes, one evening, no undo history I am proud of.
Two minutes on why we stopped animating the overshoot. Recorded on the walk home, so mind the traffic.
We cut the onboarding survey from twelve questions to four and the completion rate went from 31% to 78%. That is the headline, but the interesting part is which eight we cut and why nobody wanted to be the one to cut them. Every question had a person behind it who could explain exactly why it mattered, and every one of those explanations was reasonable on its own. The problem was never any single question. It was that twelve reasonable questions add up to something nobody will finish. So we stopped arguing about which questions were good and started asking which four we would keep if we could only keep four. That turned a two month argument into a forty minute meeting, and the four we kept are the ones we now use to route people into the right first week. The eight we dropped are still written down. We just ask them later, when someone has a reason to answer.
Prototyping the enclosure this month. Which route would you take for a run of fifty units?
Fifty units is soft tooling territory. The unit cost crosses over around forty in my experience.
Enclosure draft three, printed this morning. The corner radius is finally right and the board clears the standoffs by 0.4mm. Run of fifty starts Monday if the quote holds.
This is the clearest thing I have read about naming things in a design system. We renamed eleven components after our review and support tickets dropped by a third.
Name a component for what a person controls, not for how it is built. Nobody manages a webhook payload — they manage notifications.
Ten minutes on why our onboarding survey was lying to us — recorded on the walk home, so mind the traffic.
The density read is right. We tried the same thing with opacity and it just looked faded.
Saving this for the studio review on Thursday. Does the curve hold on a dark background?