A reading tracker that shows who you are as a reader.

Booksona · PRODUCT DESIGN · BRAND · DESIGN SYSTEM · MOTION · FULL STACK

Status: Work in progress. Beta with invited readers.

Booksona is a calm place to track your books and show who you are as a reader.

I came up with it, designed it and built it on my own: the product, the brand, the design system and the full stack behind it.

Booksona, case study cover

Properties

Role
Founder, product designer and design engineer
Team
Solo
Timeline
2026, ongoing
Platform
Web, phone and desktop
Status
Beta with invited readers
Tools
Figma, Next.js, Supabase, AI coding agents

If you read nothing else

01, Why I built it

I noticed that people in my community struggle to read books and keep track of them. There are different ways to track your reading, most notably Goodreads, but its UI/UX is extremely outdated. It’s frustrating to use, ugly to look at, and it’s Big Corpo.

Tracking just felt like homework. Logging pages in any of these apps didn’t feel good, I felt no sense of accomplishment, and I was forcing myself to read. Streaks only turned me away: if I was too busy to read, I lost everything, and I didn’t want to go through the hassle of getting it back.

So I decided to build Booksona, and it had two jobs: make tracking a book quick and pressure-free, and offer lots of rewards and customization, because as the gamer saying goes, skins = wins.

You are what you read. Booksona helps you say that, not grade you on it.

Booksona home on desktop: East of Eden in progress on a yellow card, a reading goal ring, the beta book club, and what everyone is reading

That became five rules I used to settle every design argument, in priority order:

02, The brand

I asked myself what name says books and also represents a person. Booksona instantly came to mind, funnily enough because a couple of weeks earlier I had talked to someone about their fursona.

Booksona logo sheet: horizontal and night lockups, the stacked lockup, the b sticker in every colour, and the app icons.

03, The design system

As a systems product designer, this is always on my list. I like working in a structured way: I create the components, they all live in one place, and building the app becomes a matter of dragging and dropping things into place.

Profile showpiece tiles from the Booksona design system: a holo night owl sticker earned 12 times, bookmark number 027 of 127, and a first edition bookmark numbered 18,204. Booksona components: the status pill in five states on two surfaces, sixteen mood badges and the mood chip in its states, beside the component’s code. Booksona interaction and motion: five named easing curves with their cubic-bezier values, and a table of hover, press, focus and timing for each interactive element.

04, A profile that looks like you

The profile is the showpiece, and the hardest design problem in the product: give readers real freedom without letting any profile break.

Readers get to choose a colour, a pattern, a name style, the background, the tile style and the corner shape, and can drag, resize or hide any tile, with many more customization options coming soon.

The guardrail is that every option is one I designed. Text colour switches by itself to stay readable on any choice, and a resized tile shows more content, not empty space. However a reader sets it up, it still looks designed.

A Booksona profile on desktop: the name naram ziady on a black banner with pink and yellow stars, a reading days grid, and the year’s numbers Three phone screens of one reader’s profile: a lilac daisy-patterned header with a handwritten name and the 2026 reading goal; a sticker tile and a numbered bookmark tile; friend cards and the guestbook.

05, Tracking that stays out of the way

I mapped the whole product as the Booksona Journey, from first visit to a year of reading, then spent the most time on the flows people repeat daily.

Three flows from the Booksona Journey map in Figma: first visit to first logged book, a reading session, and finding and adding a book, with each tap labelled between phone screens. Three Booksona phone screens: Home with the current book on a yellow card, the Library with books reading now, and the East of Eden book page at page 19 of 608 Three Booksona phone screens: a running session timer on the book page, margin notes from other readers with a spoiler guard, and the your reading stats page The Booksona library on desktop: 111 books with filters for reading, want to read and finished, and three books reading now with progress bars The East of Eden book page on desktop: a large cover, this read stats in yellow, purple and pink tiles, and a pages per session chart

06, Small things, earned

Rewards are where most apps add pressure. I designed them as keepsakes.

Stickers come from things you actually did, like finishing an 800-page book or reading after midnight. Earn one again and it gets shinier, from basic to holographic. Bookmarks are rarer and numbered by who got there first. You keep everything, even if you take a month off.

Stickers peel off a backing sheet, bookmarks unwrap, and pages fold with real fold geometry.

07, Reading together

The social side is small and warm on purpose: friends and clubs, not a feed of strangers.

Booksona Home on desktop: friends’ current books on the nightstand row with pages read, then the lately feed with a friend’s post, a finished book and a sticker earned, beside the next book club meet.

08, Accessibility

Accessibility was never a pass at the end. It’s built into the design system, so every new screen gets it for free, and it’s tested on every change.

The Booksona library with the Skip to content link showing after the first press of Tab. Keyboard focus ring on the Middlemarch title in the reading now section of the library, reached with the Tab key. The same Booksona book page three ways: the default font, the OpenDyslexic reading font, and dark mode.

Tested, not assumed

Automated audits catch what a machine can. The rest I find by using the app myself, and the next step is testing it with people who rely on assistive tech every day.

09, How I built it

I work as a design engineer, so I designed in Figma and shipped to production myself. I used AI coding agents to help write the code. The product decisions, the design, the specs, the review of every change and the quality bar were mine. AI is a tool that helps me achieve my vision. I never let it lead.

Of course, that only works with a strict process, so I built one:

10, What I’m learning

The app has gone through a lot of changes since the beta started. It confirmed once again that user feedback is a designer’s best friend, and it also confirmed that the product is useful.

Many users have told me that they are reading more books, that they enjoy customizing their profiles, that their stats are helpful, that seeing their friends on the home page motivates them, and that they simply enjoy using the app.

Their feedback has shaped the app into what it is today, and I couldn’t be more thankful to them.

What I’d do differently: I knowingly fell into the trap of adding too many features before testing, and I had a fun week of fixing errors and nothing else. Next time, I would launch the beta with fewer features, get those solid, and then start adding more xD

Everything here is subject to change as the beta progresses.

naram-ziady.fig · editing
autosaved ⌘K

Works

Nothing to undo. Naram has no regrets.
Suki the cat