Tarinoi has an offline-first architecture. While being able to work offline is nice, its main benefits are in the way it improves your experience online. Here we delve into the what, why and how of it.

More than branding, and never just decoration - colour is a key part of guiding users through a new interface. When so many apps compete to look the same, here's why we believe colour choices should be practical and accessible, without losing the personality behind them.

Big games have big dialogues. We've set our goal to 10,000 cards per board after which performance degrades gracefully. Here's how we got it to soldier on a long way past that.

We claim on our front page that data isolation and regulatory compliance in Tarinoi are architectural, not an afterthought. Here we elaborate on what that actually means.

How we used the Grafana stack for stress testing and observability to make sure Tarinoi can handle the concurrent users it needs to, and that it will stay running even when overloaded.

When you're in the early phase of building your project, attending conferences can feel like a low priority. We decided to attend two in a month - here's why, and what we learned.

Authors need to be able to play back their work as they're working on it. In Tarinoi, playback is integrated right into the graph. There were a few twists we had to address. Here's what we did and why.

Tarinoi isn't just a product or a project. It's about opening up a space for beautiful things to emerge. Here's why I want to make it.