The latest #AtmosphericUX from @brookie.blog, who again shows how far a designer can get by:
1. identifying a common problem,
2. describing it using minimal lexicons, +
3. shipping a tidy UX to solve it
In this case, a simple board for capturing, filtering, + making decisions from user feedback
A timely demonstration of the design pressure to improve account management UX at the PDS level
Both bsky.app + mu.social currently need the same permissions, but by supporting OAuth earlier, the fork highlights the security implications of blurring whether the app or the PDS manages your account
Handy 🧵 measuring latency for various firehose topologies
It's always nice when infra teams have optimized away every other bottleneck + you're down to the pure physics of geography
"If UI looks good, that means developers had time to polish it, which means that they probably spent a comparable amount of time to iron out the code.
It’s a heuristic, but a reasonable one." -- @tonsky.me
Given the nearly trivial setup burden for any app with an existing AT account, it's no accident that despite zero marketing + a domain that's less than a week old, she's already had several dozen creators spin up boards of their own
atproto.at/uri/at://did...
As MVPs go, this is the way