Libriax

Overview

I love books and read a lot of them, so I created Libriax as a reading tracker I could fully customise, in both features and design. It has since grown into a platform where reading behaviour can be measured, reflected on, and gently nudged.

Behavioural science motivation

The project became a behavioural science experiment in practice, asking how design can encourage sustained reading. I focused on mechanisms that influence engagement over time, such as streaks, habit cues, leaderboards, and achievements, aiming to make consistency feel rewarding without turning reading into noise.

Analytics

Libriax emphasises long-term patterns over simple book lists, with yearly views, reading time trends, and personal breakdowns that help users notice what they actually do over months of reading.

Goals and UX

The goal system was designed to make progress easy to read and easy to adjust, supporting motivation without punishing missed days. That meant iterating heavily on the small details that decide whether people actually return.

Achievements and retention

Alongside streaks, I built out a full achievements system and a leaderboard that ranks users by reading activity. These were added because the behavioural science around social comparison and completion bias suggested they would genuinely influence whether users returned. Getting the balance right required care, since gamification that feels manipulative tends to erode the very motivation it is trying to support.

To understand how users were actually behaving rather than how I assumed they were, I used SQL to query the production database directly, looking at session patterns, drop-off points, and which features saw sustained use versus initial curiosity. I supplemented this with some basic regression analysis in Python, which helped surface which variables were most predictive of users returning after the first week.

AI integration

As AI tools accelerated, I wanted to better understand them for myself. I integrated Microsoft's Phi-3 as an LLM feature inside the product, and in the process learnt practical prompt engineering, failure modes, and why retrieval, constraints, and clear product boundaries matter more than just having a powerful model.

Backend, data, and security

Building Libriax forced me to take backend fundamentals seriously such as authentication, session handling, secure routes, and the practical risks of state-changing requests. On the data side, I designed the database schema from scratch and moved from SQLite to PostgreSQL, learning how query patterns, indexes, and data integrity constraints shape both performance and reliability over time.

Lessons learnt

The biggest takeaway is that most problems are "already solved" in the ecosystem, but that does not remove the need to understand them. Using the right libraries and patterns matters, yet the real progress came from debugging, making mistakes, and learning what breaks in real usage, especially when building something with users and long-lived data.