Two Days
I built Runlight in a little over a month, and deciding what it wouldn't do shaped a lot of how it turned out.
Onboarding, interfaces, empty states, and what makes software good to use.
I built Runlight in a little over a month, and deciding what it wouldn't do shaped a lot of how it turned out.
A year ago I wrote that the habit of writing things down matters more than the software.
To delete a repo on GitHub you have to type its name in a box.
The first thing users see is the thing you designed least.
Building things only you will ever use is kinda fun.
I recently swapped a contact form for a plain mailto: link.
Why paying customers win when zero costs everything.
Every app has a chat box now...
How ownership gets manufactured before payment.
The MVP paradox: why "ship fast" advice misses the point.
Deploy a feature, watch it flop, fire up the debugger.
Why good products don't need onboarding tours at all.
Each destructive action should be reversible, not preventable.
Why free and paid are entirely different products.
The creativity recession and why everything looks the same now.
Every convenience we add creates a new dependency.
Why we need both chat and navigation.