I’ve shipped 10 apps to our team so far, including a fully custom support inbox tailoredto exactly what our team needs the second we open an email.
Yesterday a coworker asked, “I have folders — can I keep my emails in folders?” Yes, you can. I shipped it that afternoon.
When she followed up asking if she could add a new folder — because in our last support tool that meant some multi-step workaround — I got to just say: yep, type the name, hit create, already done.
That kind of turnaround is a game-changer for how we think about tools. Instead of working around limitations, now the answer can be: build it.
But not every app is mission-critical, as a team powered by books, sometimes you just need a dopamine hit of scrolling through some bookshelves and seeing what everyone’s reading.
I can’t speak to every use case out there — I’m sure there are things people want that custom apps can’t do yet. But everything I’ve needed so far, they’ve delivered, whether that’s a support tool the whole company relies on or a just-for-fun bookshelf.
One thing that makes a real difference for us: maintaining our own internal component/style reference. Fibery’s UI kit keeps the base look consistent, but working locally with that reference on top of it means every app I ship — support desk, Team Shelf, whatever’s next — actually feels like the same product instead of ten disconnected tools that happen to share a login. And it means I don’t relitigate the same decisions every time — nav placement, modal behavior, what a primary button looks like — those are settled, so starting a new app is mostly just new data and logic, not new design calls.