Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Measuring the User Experience

Measuring the User Experience

Collecting, Analyzing, and Presenting Usability Metrics
Turn usability sessions into evidence teams can trust, and decisions they can defend.
by Thomas Tullis 2008 320 pages
4.08
500+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Measure the interaction, because a poor interface can cost money or lives

Experience leaves evidence. User experience is not just a vague impression: it includes a person interacting with a product, and the resulting behavior, thoughts, or feelings can be observed and counted. Useful measures include whether tasks succeed, how long they take, what errors occur, and how users rate the experience. Together, these reveal effectiveness, efficiency, and satisfaction.

The stakes are real. In a study of automatic defibrillators, a quarter of participants using one machine could not deliver a shock successfully. In a charitable-giving website redesign, overall donations rose by 50%, while recurring donations increased from 2 to 19. Measurement made obstacles and improvements visible, giving teams evidence to act on rather than relying on hunches.

Analysis

What's important is not that every human response can be reduced to a number, but that important design claims can be tested. A count of failed tasks does not explain what a user experienced, yet it can make a hidden risk impossible to dismiss. The strongest use of metrics is therefore accountability: connect a measurable interaction to a human consequence, then investigate what caused it. The defibrillator example also sets a useful boundary. A reassuring average cannot substitute for examining rare, severe failures when the cost of one mistake is high.

Choose metrics only after deciding what the study must change

Begin with the decision. A study may be formative, meaning its findings are used to improve a design before release, or summative, meaning the product is assessed against goals or compared with alternatives. Formative work benefits from quick cycles: find a problem, make a change, and test again. Summative work needs clear criteria and planned follow-up, so results lead to a decision rather than a report that sits unread.

Include user goals. Someone using a tool every day may care most about time and effort. A person choosing among shopping sites may also care about confidence, satisfaction, and whether the experience met expectations. The method and metrics should follow both the study's purpose and what users are trying to accomplish.

Analysis

This decision-first approach prevents measurement from becoming a ritual. A metric is useful when it changes a choice, establishes a baseline, or helps locate an obstacle. Otherwise, it may simply add charts to a project. The formative and summative distinction also clarifies why one study cannot always serve every purpose: a small, exploratory test can expose design trouble without proving population-wide performance. One further question is whose goals shape the criteria. A business target can be measurable and still overlook what matters to users, so both should be made explicit.

Pair task performance with user sentiment, because they can disagree

Behavior and opinion differ. Performance measures what users do, such as completing a task, making errors, or taking time. Self-reported measures capture what users say or feel, such as ease, confidence, or satisfaction. Neither can stand in for the other. Across ten online usability studies, correlations between task time and ease ratings ranged from -0.41 to +0.06. Correlations between task success and ease ratings ranged from 0.21 to 0.65.

Look for the mismatch. Users may fail while believing they succeeded, or complete a task correctly while feeling frustrated. A scorecard showing task success beside ease ratings can expose this gap. It is especially important when a wrong answer looks plausible to the user, because confidence alone can conceal a serious failure.

Analysis

The disagreement between what users do and what they report is not a flaw to average away. It can reveal different parts of the experience: whether the interface supports the task, whether users recognize success, and whether the process feels acceptable. A high satisfaction score alongside poor performance might reflect a pleasant interface, low expectations, or misplaced confidence. The data do not decide which explanation is right; observation and follow-up questions do. Treating the measures as complementary keeps a polished impression from masking a broken task.

Show uncertainty; a small sample can make an impressive percentage fragile

Know what the data allow. Data type determines which summaries and comparisons make sense. Task success is categorical, satisfaction rankings are often ordinal, and time is ratio data. Counts and percentages suit categories; averages and tests for means require stronger measurement assumptions. For a sample average, a confidence interval communicates how imprecise the estimate may be. It generally narrows as sample size grows or data variability falls.

Percentages can mislead. Four successes among five participants is an 80% success rate, but its 95% adjusted Wald confidence interval runs from 36% to 98%. The same percentage based on many more participants is more informative. Show intervals or the underlying counts, use a statistical comparison suited to the data, and avoid reporting meaningless decimal precision.

Analysis

The interval changes the story from “80% succeed” to “the estimate remains highly uncertain.” That distinction matters because a sample statistic is not a guarantee about every future user. Statistical significance also does not establish that a difference matters in practice; the size of the effect and the consequences of the task still matter. Confidence intervals make uncertainty visible, but they cannot repair unrepresentative recruitment, poorly defined tasks, or contaminated data. Good analysis begins before calculation, with a clear account of whom the sample represents.

Count issues consistently, but never mistake severity ratings for objective truth

Make problems actionable. A usability issue should connect observed behavior to a plausible interface cause. “Users misunderstood the navigation and searched several sections” gives a design team somewhere to investigate; an abstract claim about mismatched mental models may not. Teams can track unique issues, how many participants encounter each issue, and whether issues cluster around particular tasks or categories.

Expect disagreement. In one comparative evaluation, only 1 of 141 reported problems was identified by all four teams, while 128 were found by just one team. Severity ratings can help prioritize work, but evaluators do not always agree on them. Five participants may be enough to find prominent problems in a small, focused formative study, but not when the product, audience, or consequences are broad.

Analysis

Counting issues adds useful structure to a practice that often depends on expert interpretation. Yet the comparative findings show why issue counts should not be presented as a complete inventory of reality. What evaluators notice depends on the tasks, participants, and expectations they bring. More participants can help, but broader task coverage and an independent reviewer may reveal different problems. Severity is best treated as a disciplined prioritization aid, supported by clear criteria and discussion, rather than as a scientific verdict that removes judgment.

Track task success, effort, and learning, not speed alone

Choose performance measures that fit. Task success requires a defined end state. For a critical task, binary success may be appropriate; for other tasks, partial success can reveal useful progress. Errors should also be defined in advance, including which actions count and whether multiple mistakes can occur. Efficiency can be measured through time or through actions such as clicks, page visits, or button presses.

Measure change with experience. Learnability is assessed by tracking a performance measure over repeated trials. In a fingerprint self-capture study, participants completed tasks in about a minute and a half, and their performance improved between attempts. Faster is not automatically better: speed may undermine accuracy in a safety-critical process, while an educational task may benefit from deliberate time. Interpret time in light of the user's goal.

Analysis

These measures distinguish “can users do it?” from “how much does doing it cost them?” and “how quickly do they improve?” That distinction is valuable for products used repeatedly, where a poor first encounter may become efficient only after extensive practice. A task-time target should therefore reflect the context, not a universal preference for speed. Counting clicks is similarly imperfect: fewer actions can mean less effort, but a well-placed confirmation step may prevent a costly mistake. Efficiency needs a meaningful definition of effort and outcome.

Ask about each task immediately, then use a validated scale for the whole product

Capture the local experience. A brief post-task question can identify which activity felt difficult while the encounter is still fresh. The Single Ease Question asks users to rate a completed task on a scale from very difficult to very easy. An expectation measure adds a useful comparison: ask how easy users think a task will be, then how easy it actually felt. Tasks that seemed easy but proved difficult are clear candidates for repair.

Capture the overall impression. The System Usability Scale uses ten statements to produce a score from 0 to 100. Across two large collections of studies, median scores were 69 and 71. The Net Promoter Score instead groups recommendation ratings into detractors, passives, and promoters, then subtracts the detractor percentage from the promoter percentage. That simplification is convenient, but loses detail.

Analysis

Task-level ratings help locate friction; an end-of-session scale captures a broader impression. The distinction is useful because memory and overall judgment can blur specific moments. Standardized questionnaires also make comparisons easier, though a familiar score should not be mistaken for a complete diagnosis. Recommendation likelihood is not the same as usability, and compressing an eleven-point response into three groups discards information. Self-report is most informative when it is attached to a clear question, interpreted alongside behavior, and collected in a way that reduces pressure to please the moderator.

Use live-site experiments to test small changes and locate abandonment

Watch the real journey. Website analytics can show where users enter, click, continue, or leave a process. Drop-off rates help identify the step where a transaction loses users; click-through rates show how often a displayed link or button is selected. These measures describe behavior at scale, but usually cannot explain why it happened.

Test a specific change. In an e-commerce example, changing a button's wording increased clicks by 24% and revenue per visitor by 48%. A useful A/B test sends comparable visitors to alternatives at the same time, ideally by random assignment, and tests whether outcomes differ reliably. Small changes make results easier to interpret. When one version wins, adopt it and continue testing rather than treating one experiment as a universal design rule.

Analysis

Live experiments are powerful because they observe choices in the setting where those choices matter, rather than asking users to imagine them. Their scale can reveal effects that a small lab study would miss. But a click is not automatically a benefit: more clicks might reflect confusion, and a revenue gain does not explain what users valued. Random assignment supports a stronger comparison than testing one design in the morning and another later, but interpretation still depends on choosing an outcome that represents a good experience, not merely a convenient business proxy.

Combine scores only when their weights and assumptions are visible

Make the recipe inspectable. Teams can combine measures by checking whether each participant meets a set of goals, converting measures to a common percentage scale, or standardizing them as z scores. A specialized Single Usability Metric combines task completion, time, errors, and post-task satisfaction. A scorecard can instead show several measures side by side, preserving more of the detail.

Beware the average. In one example, average task success and average time appeared to meet targets, but only 38% of participants met both targets together. A composite score can conceal that kind of mismatch. Equal weighting is a choice, not a natural fact; the relative importance of success, time, and satisfaction should follow the product's purpose. Set goals before testing when possible.

Analysis

A summary score can help a busy decision-maker see a pattern, but every composite embeds judgments about trade-offs. If a high satisfaction score can compensate for failed critical tasks, the formula may hide the very risk the study should expose. Showing separate measures alongside the combined value makes the construction auditable. Goal-based reporting is often easier to interpret because it asks whether a defined standard was met, though the standard itself still deserves scrutiny. A scorecard should compress evidence, not erase the reasons behind it.

Triangulate user tests with field behavior and accessibility needs

Use evidence that sees different things. A lab session reveals what users try and where they struggle. Field analytics show what visitors actually do across many visits. At the Open University, tracking showed that 37% of visits involving Information Technology also involved Computing, while only 27% of Computing visits involved Information Technology. This supported usability observations that the original subject list obscured related choices and informed a revised organization.

Include overlooked users. Accessibility is usability for people with particular access needs. Test with representative users where possible, and assess relevant standards such as the Web Content Accessibility Guidelines. Automated checks can catch some code problems, but human inspection and assistive technology are needed to judge many issues. Eye tracking or biometric signals can add evidence, but they do not explain a user's experience on their own.

Analysis

Triangulation is valuable because each method has a different blind spot. A test can reveal confusion without showing how often it happens in the wild; analytics can show abandonment without explaining its cause. Agreement across sources strengthens a conclusion, while disagreement can expose a hidden assumption. The biometric example in the book makes the point vividly: greater arousal while using a printed textbook was interpreted as difficulty only after reaction cards and discussion supplied emotional context. More instrumentation is not the same as more understanding.

Translate findings into business outcomes, while labeling every assumption

Connect evidence to consequences. A redesign of a state government portal raised average task success from 72% to 95% and reduced average task time from 2.2 minutes to 0.84 minutes. The team then estimated savings in public time and additional transaction revenue. Those projections depended on assumptions about how many residents used the site and how often they made paid transactions, so observed usability gains were firmer than the financial extrapolation.

Make the evidence memorable. Show a few clear metrics, explain their meaning, and support them with examples or short clips of users encountering the same issue. Establish consistent benchmarks across releases, and tailor the presentation to the audience. Managers may need a cost or revenue implication; designers need the specific behavior and an actionable recommendation.

Analysis

Business translation helps UX evidence compete for attention and resources, but it also creates a temptation to overstate causal certainty. A shorter task time is a measured result; a projected annual saving depends on traffic, repetition, and assumptions about the value of time. Keeping those layers separate strengthens credibility rather than weakening the case. Stories and clips can make data legible, while the numbers test whether a memorable anecdote is representative. The strongest presentation lets decision-makers see both the human obstacle and the limits of the estimate.

Analysis

The book's central contribution is to make user experience an operational subject without pretending that every part of it is simple. It gives practitioners a path from a question, to a study design, to evidence, to a decision. Its enduring strength is pluralism: task success, time, errors, satisfaction, field analytics, and physiological responses are treated as different windows onto an interaction, not interchangeable definitions of quality.

That pluralism also creates a responsibility. Every metric is an operational definition, a choice about which part of experience counts and how it will be recorded. A completion rate depends on a chosen success criterion. A severity score depends on a rubric. A composite score depends on weights. The procedure may be consistent while the construct remains incomplete. Measurement rigor therefore requires documenting the definition, the sample, exclusions, and assumptions, not merely presenting a precise-looking output.

There are three especially important cautions. First, a confidence interval describes uncertainty in an estimate under a statistical model; it does not mean that 95% of individual users will fall inside the interval. Second, combining measures can create compensation where none is acceptable. High satisfaction should not offset a safety-critical failure. Third, an A/B test can establish that a change affected a selected outcome under tested conditions, but the outcome may not capture user welfare. Optimizing clicks, time, or revenue alone can reward an experience that is more manipulative or merely more attention-grabbing.

The book's practical stance is strongest when metrics support interpretation rather than replace it. Qualitative observation explains what a number means; field data tests whether a lab pattern matters at scale; accessibility testing asks whose experience is missing. The mature goal is not a single score or a dashboard full of measures. It is a repeatable learning system that makes uncertainty visible, connects design choices to consequences, and changes course when evidence contradicts intuition. Sensitive behavioral and biometric data also warrant clear consent and restraint, especially when inferred emotions could affect users beyond the study.

Summary in 30 Seconds
Measure task completion, errors, time, and user ratings because behavior and opinion can diverge. Small samples produce uncertain estimates: four successes among five people yield an 80% rate, but the adjusted 95% interval spans 36% to 98%. A/B tests can connect interface changes to outcomes, while analytics reveal where visitors leave. Combine measures cautiously, preserve their assumptions, and check lab findings against real-world behavior and accessibility needs.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.08 out of 5
Average of 500+ ratings from Goodreads and Amazon.

Measuring the User Experience receives mostly positive reviews, with readers praising its well-structured content and clear explanations of UX metrics and statistics. Many find it a valuable resource for UX professionals, particularly those new to quantitative research. The book is described as comprehensive, practical, and useful for planning usability studies. Some readers note its textbook-like nature, which can be both a strength and a drawback. A few critics find it too basic, but overall, it's highly recommended for those looking to improve their understanding of UX measurement and data-driven decision-making.

Your rating:
4.51
274 ratings
Want to read the full book?

Glossary

UX metrics

measures of interaction

Quantifiable observations about a person's interaction with a product or system. Common examples include task success, time, errors, satisfaction ratings, and visual attention. A useful UX metric must be observable, consistently collected, and connected to some aspect of the user's experience, such as effectiveness, efficiency, or satisfaction.

Formative usability

testing to improve design

Evaluation conducted while a product or design can still be changed. Researchers identify obstacles, recommend adjustments, and assess the revised design in iterative cycles. Its value depends on the team having an opportunity to act on findings, so it is most useful before a design is finalized or released.

Summative usability

evaluation against goals

Evaluation used to judge how well a product meets predefined usability objectives or compares with another product or release. It emphasizes assessment rather than diagnosing changes during development. Useful summative work defines its criteria in advance and plans what decisions or actions will follow from the results.

Single Ease Question

post-task ease rating

A one-item measure of perceived task difficulty, asked after a participant completes a task. The participant rates how difficult or easy the task was, commonly on a seven-point scale. It is designed to be quick to administer and can help compare perceived difficulty across tasks or design versions.

System Usability Scale

overall usability questionnaire

A standardized questionnaire developed by John Brooke to assess perceived usability. It contains ten statements, with positive and negative wording, rated on a five-point agreement scale. Responses are converted into a score from 0 to 100. The score supports comparison across studies, but is not itself a diagnosis of specific usability problems.

Net Promoter Score

recommendation-based loyalty measure

A customer metric based on likelihood to recommend a company, product, or service, rated from 0 to 10. Ratings of 0 to 6 are classified as detractors, 7 or 8 as passives, and 9 or 10 as promoters. The percentage of detractors is subtracted from the percentage of promoters, producing a score from -100 to +100.

lostness

navigation inefficiency measure

A measure of how inefficiently a user navigates a website while trying to complete a task. It uses the number of distinct pages visited, total page visits including revisits, and the minimum pages needed for the task. A score of zero represents an ideal path; higher values indicate more deviation from that path.

Areas of interest

defined gaze regions

Specific regions of a screen or scene selected for eye-tracking analysis. Researchers define each region using coordinates, then examine measures such as whether participants looked at it, how long they looked, or how quickly they first fixated on it. Careful boundaries matter because adjacent or overlapping regions can distort comparisons.

Single Usability Metric

combined usability score

A method developed by Jeff Sauro and Erika Kindlund for combining standardized measures of task completion, task time, errors, and post-task satisfaction. The measures are combined at the task level to produce scores for individual tasks and an overall result. The score simplifies comparison but should be interpreted alongside its component measures.

A/B test

randomized design comparison

A live-site experiment that compares two versions of a page or interface element by exposing different visitors to each version and measuring outcomes such as clicks, purchases, or abandonment. Random assignment and concurrent testing help make the comparison fair. The result identifies differences in measured outcomes, but does not by itself explain why users responded differently.

Adjusted Wald Method

interval for success rates

A method for calculating confidence intervals around proportions, such as the percentage of participants who complete a task successfully. It was recommended in the book for usability studies with small samples because other interval methods can perform poorly at those sizes. The interval shows uncertainty around the estimated proportion, not variation among individual outcomes.

FAQ

What's Measuring the User Experience about?

  • Comprehensive Guide: The book is a detailed guide on collecting, analyzing, and presenting usability metrics to enhance user experience across various products and systems.
  • Practical Focus: It emphasizes practical applications of UX metrics, making it accessible for professionals who need actionable insights rather than theoretical discussions.
  • Diverse Metrics: Covers a wide range of metrics, including performance, self-reported, and issue-based metrics, to effectively evaluate user interactions.

Why should I read Measuring the User Experience?

  • Improve Design Processes: It helps readers understand how to measure and enhance user experience, crucial for product success in a competitive market.
  • Expert Insights: Authored by seasoned professionals Tom Tullis and Bill Albert, it shares insights from over 40 years of combined experience in UX research.
  • Broad Applicability: The methodologies are applicable to a wide range of products, from websites to consumer electronics, making it relevant for many professionals.

What are the key takeaways of Measuring the User Experience?

  • Importance of Metrics: Highlights that UX metrics are essential for understanding user behavior and improving product design, preventing decisions based on incorrect assumptions.
  • Types of Metrics: Categorizes metrics into performance, issue-based, and self-reported, each serving a unique purpose in evaluating user experience.
  • Practical Guidelines: Offers practical advice on collecting and analyzing data, ensuring readers can implement these strategies in their work.

What are some common myths about UX metrics discussed in Measuring the User Experience?

  • Time Consumption Myth: Dispels the myth that metrics take too much time to collect, explaining that simple metrics can be integrated into regular evaluations.
  • Cost Misconceptions: Addresses the belief that UX metrics are costly, emphasizing that valuable data can be collected affordably through various methods.
  • New Products Misunderstanding: Clarifies that metrics are applicable to new products, arguing that establishing baseline metrics is critical for future comparisons.

How does Measuring the User Experience define user experience metrics?

  • Quantifiable Measures: Defines UX metrics as quantifiable measures that reveal aspects of user interactions, such as effectiveness, efficiency, and satisfaction.
  • Observable and Quantifiable: Stresses that all UX metrics must be observable and quantifiable, allowing them to be turned into numbers or counts for analysis.
  • Decision-Making Tool: States that UX metrics provide answers to essential questions about user behavior, aiding informed decisions about product design.

What types of performance metrics are covered in Measuring the User Experience?

  • Task Success: Measures how effectively users can complete tasks, discussing both binary success (success or failure) and levels of success (partial success).
  • Time on Task: Emphasizes measuring how long it takes users to complete tasks, a key indicator of efficiency.
  • Errors and Efficiency: Covers the measurement of errors made during tasks and overall efficiency, combining task success with time taken.

How can I effectively present UX metrics according to Measuring the User Experience?

  • Visual Representations: Recommends using graphs and charts to visually represent data, making it easier for stakeholders to understand findings.
  • Include Confidence Intervals: Suggests presenting confidence intervals alongside metrics to convey data reliability.
  • Focus on Key Findings: Highlights the importance of emphasizing significant findings and trends to ensure the audience grasps design implications.

What is the System Usability Scale (SUS) in Measuring the User Experience?

  • Widely Used Tool: Described as a widely used tool for assessing perceived usability, consisting of 10 statements rated by users on a five-point scale.
  • Scoring Method: Involves summing score contributions from each item and multiplying by 2.5 to obtain an overall score on a scale of 0 to 100.
  • Score Interpretation: Provides guidelines suggesting scores below 50 are not acceptable, while scores above 70 are considered acceptable.

How can I effectively collect self-reported metrics according to Measuring the User Experience?

  • Standardized Questionnaires: Recommends using standardized questionnaires like ASQ, CSUQ, and QUIS for structured user feedback.
  • Open-Ended Questions: Suggests including open-ended questions to allow users to express thoughts and feelings, providing richer qualitative data.
  • Data Analysis: Emphasizes analyzing collected data to identify trends and insights, informing design decisions and improving user experience.

What are the best practices for conducting usability tests as outlined in Measuring the User Experience?

  • Plan Ahead: Stresses the importance of early planning, including defining success criteria and determining which metrics to collect.
  • Engage Stakeholders: Encourages involving stakeholders in the testing process to help them understand user experiences firsthand.
  • Iterate Based on Findings: Suggests an iterative process where findings from one round inform improvements for the next, enhancing design quality.

What is the significance of eye tracking in Measuring the User Experience?

  • User Attention Insights: Provides insights into where users focus their attention, helping identify engaging or confusing elements.
  • Common Metrics: Discusses metrics like dwell time, number of fixations, and time to first fixation to assess user engagement.
  • Data Visualization: Emphasizes visualizing eye-tracking data through heat maps and gaze plots to communicate findings effectively.

How does Measuring the User Experience address the concept of usability ROI?

  • Calculating ROI: Discusses methods for calculating ROI for usability improvements, linking metrics to business outcomes like increased sales.
  • Case Studies: Provides case studies illustrating successful measurement of financial impact from usability enhancements.
  • Practical Framework: Offers a framework for calculating usability ROI, including identifying cost savings from improved efficiency and satisfaction.

About the Author

Bill Albert is an author and expert in the field of user experience (UX) design and research. He is known for his work on measuring and quantifying user experience, particularly through his book "Measuring the User Experience." Albert's approach combines statistical analysis with practical UX methodologies, making complex concepts accessible to professionals in the field. His work is highly regarded in the UX community, as evidenced by the positive reception of his book. Albert's expertise lies in translating academic principles of human-computer interaction into practical applications for industry professionals, bridging the gap between theoretical knowledge and real-world UX practices.

Download PDF

To save this Measuring the User Experience summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.41 MB     Pages: 22

Download EPUB

To read this Measuring the User Experience summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.38 MB     Pages: 28
Want to read the full book?
Follow
Listen12 mins
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 25,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...