The library view is the heart of SavePosty — the grid where everything you’ve saved actually lives. I gave myself a weekend to ship a version good enough to use every day. Here’s what made the cut and what didn’t.
The three things that had to work
A “save it for later” tool is worthless if finding things later is slow, so I picked three non-negotiables and built nothing else until they felt right.
- Auto-fetched thumbnails. A wall of text is hard to scan; a wall of covers is instant. On save, a background job pulls the Open Graph image and falls back to a generated card when there isn’t one.
- Full-text search. Not just titles — the captured article text too, so you can find the thing you half-remember by a phrase from the middle of it.
- Keyboard navigation. Arrow keys to move, Enter to open,
/to focus search. Once your hands stay on the keyboard, the whole tool feels faster than it actually is.
What I cut to ship
The weekend deadline did its job by forcing cuts. Collections-within-collections, shared libraries, and a bulk-tagging UI all got pushed. None of them block daily use, and shipping the core meant I started living in the tool — which surfaced better priorities than my original backlog ever would have.
The lesson, again
Every time I time-box a feature, the constraint writes a better spec than I do. The library view I’d have designed with unlimited time would have been more impressive and less used. Ship the spine, live with it, let real friction tell you what’s next.