LYBRIX APP

LYBRIX APP

Multimodal reading app

Academic team project

A multimodal reading app for people whose time, focus and eyesight change from day to day. Competitive analysis, a focus group, personas and user needs shaped the information architecture, two key user flows and wireframes tested in Maze.

Role

Main designer and lead UX contributor

Deliverables

Competitive analysis, Empathy map, Personas, User need statements, Focus group review, IA diagram, Two user flows, Low-fidelity wireframes, Interactive prototype

01 The brief

Reading apps are built around progress tracking, streaks and a single format. For people with limited time, fluctuating focus or visual strain, that turns reading into a source of pressure rather than support.

LYBRIX set out to address three problems: systems that pressure the reader instead of adapting to them, weak support for moving between text and audio, and the gap between digital reading and physical books.

Audience: people whose available time, focus and eyesight change from day to day.

02 Research

Competitive analysis, empathy mapping, personas, user need statements and a focus group review produced four needs:

  • Easier access to content straight from Home
  • Smooth switching between reading and listening
  • A calmer system, without streaks, pressure or guilt
  • Better support for exchanging and reusing physical books

Limitation: these came from a focus group review and secondary research rather than a recruited study, and the number of participants is not recorded in the project documentation. They are a well-grounded starting point, not measured demand.

03 Strategy

The principle was to remove pressure from the system rather than add features to it: format becomes a choice made in the moment, progress is an intention rather than a streak, and the physical and digital library belong to one experience.

04 What I made

Information architecture. Four areas — Home, Library, Reading, and Account and Preferences — covering daily reading intention, in-progress and completed reading, both reading modes, exchange management and preferences. The structure treats reading as an adaptable state rather than a linear task.

LYBRIX information architecture diagram showing Home, Library, Reading, and Account and Preferences
Information architecture: four areas, with reading treated as a state rather than a sequence.

User flows. Two carried the most weight: switching from reading to listening, and setting a daily reading intention.

User flow for switching from reading to listening
Flow 1: switching from reading to listening without losing position.
User flow for setting a daily reading intention
Flow 2: setting a daily reading intention, which replaces streak tracking.

Home and the reading interface. Home leads with in-progress access, daily intention and recommendations that support resuming rather than restarting. The reading interface is one adaptive environment for text and audio, with bookmarking, playback controls, transcripts and adjustable settings.

Low-fidelity wireframes of the LYBRIX home and reading interface
Selected low-fidelity wireframes: home and reading interface.
Further low-fidelity wireframes of the reading interface across mobile and tablet
Reading interface across mobile and tablet, showing multimodal controls.

A broader low-fidelity system was produced; these are the screens that carry the core structure.

05 My contribution

As main designer and lead UX contributor I owned the structural foundation: the information architecture, the two key user flows, and the selected low-fidelity wireframes used for early validation. I also contributed to research synthesis and the focus group analysis.

The visual design and the remaining wireframe screens were team work.

06 Results

Completed and documented: research synthesis, information architecture, two key user flows, selected low-fidelity wireframes, and an interactive prototype taken into early validation.

Each research finding is traceable to a structural decision: Home leads with in-progress reading and a daily intention; one reading interface carries both text and audio; daily intention replaces streak tracking; and book exchange is built into the architecture rather than bolted on.

Maze testing was run on the low-fidelity prototype to check navigation and task clarity. The task results were not retained in the project documentation, so no completion rates or usability scores are presented here.

07 Reflection

Two limits are worth stating plainly. The prototype was deliberately low fidelity, so testing could only tell us whether the structure and labels made sense — not whether the interface felt good to use. And the project stayed in development rather than reaching a release.

The question I would take further is the one the architecture rests on: whether replacing streaks with a daily intention actually keeps people reading over weeks, or only removes the guilt of stopping. That needs a diary study, not a usability test.

An opportunity to contribute

I'm interested in joining teams working across digital marketing, content, audience research, and web-based communication. I bring experience from research-informed projects, practical digital work, and collaborative documentation, with an interest in developing these capabilities in a professional environment.