After shipping big things, I'm in my small things bag for the next two weeks. Yesterday, I shipped an optimization to make interacting with cards on big spaces way faster. The extra responsiveness is a hugely noticeable on my old ass phone.

Speaking of phones, I'm midway through working through a fix for dialogs not showing up/getting clipped when you pinch zoom too far in or out on a touch screen. Unfortunately there's no css-only way to define max heights in a way that properly compensates for changes to viewport scale. e.g. when the screen is pinched out to a 0.5 viewport ratio, an element defined as having a height like 100vh - 100px, the intents of vh and px numbers get ignored, or changed in pretty mysterious ways.

We're on the bleeding edge.

So the answer is some tiny, fast, fallback js to properly compute max-heights. This might not make sense to anyone but me, I'm not even sure it makes sense to me...

But my fallbacks (mostly) work and the pinch card experience feels a lot better in my prototype.

I've been heads down designing/building card tagging for what feels like forever, but really has just been a week. There's still lots to go, but the hardest work is all done,

Almost all the UI is complete. You can
- type [[ to add or select tags, it's all keyboard drivable so you don't have to move your hands too much if you don't want to
- filter cards by tags,
- click a tag to see all the other cards with that tag from all your spaces,
- change the color of a tag, which is applied universally across all your spaces

So what's left?

• review the client code so far (it's still fresh in my mind and totally functional so it's a good time to clean it up)

After that, it's mostly ~server~ stuff
- add the tag models to the database
- add routes and related logic
- add websocket broadcasting update events for collaboration to the client app

Test the hell out of it. Especially on mobile, and with collaboration.