Booka App

Shazam For Books

Whenever you are looking to buy a book and you aren't sure about the details, that is where Booka app comes to help!

Role

Product Designer


Concept Type

Concept App

Personal

Scope

UX/UI

Research

Prototyping

Date

June 2025

Overview

Have you ever entered a bookstore and just wanted to explore some book titles that you didn't know anything about? If you did, usually, you would have to pull out your phone and search for information online and go trough multiple pages, filter through irrelevant results and piece together fragmented information to see what the book is actually about. Even for just one title, that seems like a lot of work, let alone if you wanted to browse multiple books. No matter if it is just for one or multiple books why not make it quicker?

What problem is being solved?

What problem is being solved?

Core problem

Core problem

The problem is that in-store book discovery lacks instant, structured insight that supports quick and confident decision-making. There is no dedicated “scan and understand instantly” experience for books, comparable to the simplicity of Shazam for music.

Pain points

Pain points

📱 Manually type book titles into search engines

↔️ Jump between Goodreads and other similar websites

🔍 Filter through irrelevant results

🧩 Piece together fragmented information

What is the goal of this project?

What is the goal of this project?

The goal

The goal

Help users make faster, more confident book purchase decisions in physical stores and to bridge the gap between instinctive, emotional exploration and informed decision-making, so users can quickly validate their choices, feel assured in their selections, and leave the store satisfied with books they’re excited to read.

To achieve

To achieve

⏱️ Enable book information through cover scan in under 5 seconds

🧾 Present concise, structured information optimized for quick scanning

📚 Reduce the need to leave the physical browsing

❤️ Preserve the emotional flow of bookstore discovery

Who are the users?

Who are the users?

The users

The users

People who want to explore buying physical books in a store either for themselves or as a gift. Across all users, the common behavioral thread is a desire for fast, low-effort validation within the physical browsing moment, without disrupting the natural flow of discovery.

Shared behaviour

Shared behaviour

📲 Mobile-first

📸 Comfortable using camera tools

⚡️ Value quick answers over deep research while shopping

What is the user's behaviour?

What is the user's behaviour?

The behaviour

The behaviour

The primary users are frequent bookstore browsers who enjoy discovering books visually rather than through search. They are drawn in by covers, typography, and shelf placement, often picking up multiple titles out of curiosity. Their decision-making process is fast and emotional at first, but they seek quick validation before committing to a purchase. Secondary users exhibit similar patterns but with different motivations.

Gift buyers browse with uncertainty, looking for reassurance that a book is appropriate or has good rating without needing deep literary analysis. Casual readers hesitate more and seek clarity about genre, tone, or themes before committing. Some are especially concerned with practical details. Such as avoiding buying the wrong edition or unknowingly starting in the middle of a series.

How is the problem being solved?

How is the problem being solved?

The solution

The solution

The app is designed around a single, frictionless interaction: scanning a book cover. Users open the app directly to the option to scan the book with no distractions or secondary navigation, mirroring the simplicity and instant feedback of Shazam. To optimize for in-store use, the interface accounts for environmental factors such as lighting, fast camera autofocus, clear loading feedback (“Identifying book…”), and offline fallback messaging.

Once a book is recognized, results are presented in a concise, skimmable format, emphasizing the most relevant information so users can understand a book in under 10 seconds. The experience preserves the emotional momentum of browsing by avoiding ads, overloaded review feeds, or endless scrolling, supporting rather than replacing the in-store discovery process. Finally, edge cases like multiple editions, similar covers, false recognition, or books missing from the database are addressed.

Scan Results

1/6

Scan Results

1/6

What is currently out there in the market?

What is currently out there in the market?

Competitive analysis

Competitive analysis

Currently in the market there is no such app that delivers quick and instant information. Apps such as Goodreads, Sumsy, BookLens and Book Scan give you an option to scan a book cover, but they all fail to provide the speed and concise information. Unlike review-heavy platforms, here the user-generated content was intentionally removed to preserve speed and reduce cognitive overload.

These options weren't built for this specific case, hence you still have to browse around multiple resources to get to the point of decision making. Book Scan is one of them, but is not free and the UX/UI has room for improvement.

Design

Design

The design approach

The design approach

The main idea was to design a minimal, modern and clean mobile application that feels calm, intelligent, and intentional. The inspiration behind the palette was an old book and wooden shelves in a bookstore, hence the very light warm yellow background with dark brown text. I almost completed a whole dark version of the app but decided to pivot since the emotional feel and background for this type of app didn't feel right for it to be just another black modern application. This palette spoke more to the world of books.

What have I learned?

What have I learned?

Information hiearachy

Information hiearachy

At the start, I explored richer, more content-heavy screens. Quickly, it became clear that the core value of the product wasn’t depth, but immediacy. This forced me to make stricter decisions about hierarchy, progressive disclosure, and what not to show. Reducing information is often more impactful than adding it.

Designing with real-life constraints in mind

Designing with real-life constraints in mind

Even as a conceptual project, considering technical limitations (like incomplete metadata, API dependencies, and scan reliability) changed how I approached edge cases and empty states. I started designing not just for ideal scenarios, but for failure modes as well. I incorporated the principles of atomic design, hence it can work with or without particular information that is not universal to every book.

Leaving ego a the door

Leaving ego a the door

The strongest improvements didn’t come from initial ideas, but from refining flows, simplifying decisions, and removing unnecessary steps. This reinforced the importance of testing assumptions and being willing to discard ideas that don’t hold up.