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
Broad Band

Broad Band

The Untold Story of the Women Who Made the Internet
In 1946, ENIAC solved a problem in seconds after women spent weeks teaching it how.
by Claire L. Evans 2018 288 pages
3.93
2k+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Tell computing history through the people who made machines useful

The job came first. In an 1892 newspaper ad, the Naval Observatory sought a “computer,” meaning a person hired to calculate by hand. Women filled these roles in astronomy, military research, and science. At Harvard, a team of women classified thousands of stars; at NASA’s predecessor, Katherine Johnson calculated flight paths for astronauts. Their collective work made large scientific projects possible, but individuals often received little recognition or pay.

Users give machines meaning. The book follows women from human calculation to programming, networking, online communities, and game design. Across these eras, their contributions often centered on making technology useful to other people. The history of computing, Evans argues, cannot be told through machines and celebrated inventors alone. It must also include the people who organized, programmed, explained, and used them.

Analysis

What is striking is how often technical history treats visible hardware as the main event and the work that makes it usable as background. This account reverses that hierarchy without claiming that women possess some natural gift for user-focused design. The more useful question is institutional: which kinds of labor get called invention, and which get filed under support? That distinction matters because credit shapes hiring, pay, and whose ideas become the next generation’s starting point.

See programming in the loom, not just in the machine

Patterns became instructions. In the early nineteenth century, Joseph-Marie Jacquard’s loom used punched cards to reproduce intricate textile designs. The cards separated a pattern from the machinery that carried it out, an idea Charles Babbage adapted for his proposed calculating engines. The loom’s history also points to women’s longstanding skill in weaving, a practice that joined materials, sequence, and design.

Ada imagined general-purpose computing. In her notes on Babbage’s unfinished Analytical Engine, Ada Lovelace explained that a machine manipulating symbols might process more than numbers. She described a procedure for calculating Bernoulli numbers, often recognized as an early computer program. The engine was never completed, but its planned input, storage, processing, and output anticipated elements of modern computers.

Analysis

The loom offers a powerful way to see computation as a relationship between instructions and execution, rather than as a box that mysteriously produces results. Lovelace’s contribution is especially significant because she reasoned about what symbolic machines could represent, not merely what one machine could calculate. Historical credit can still become a contest over who was first. The stronger lesson is that ideas about computation emerged through networks of tools, people, and explanation.

Credit the programmers whose labor made ENIAC useful

The machine needed translators. Grace Hopper learned to program Harvard’s Mark I during World War II, writing code, documenting the machine, and finding reusable sequences called subroutines. At the University of Pennsylvania, six former human computers learned to program the ENIAC, a far faster electronic computer. They worked out how to configure it, diagnose faults, and translate mathematical problems into operations the machine could perform.

Speed concealed preparation. For a 1946 public demonstration, Betty Jean Jennings and Betty Snyder spent weeks preparing a ballistics program. The ENIAC completed the calculation in about twenty seconds, but news coverage credited the machine and omitted the women’s work. The six were not invited to the celebratory dinner. The episode shows how the impressive output of a computer can hide the human expertise required to produce it.

Analysis

The ENIAC story makes a useful distinction between computation and the preparation that enables it. A fast result is not an explanation of how that result became possible. The same accounting problem appears wherever organizations celebrate outputs while treating maintenance, testing, documentation, and coordination as peripheral. Restoring these contributions is more than symbolic fairness: it gives a truer picture of how complex systems work and where their reliability comes from.

Make computers easier to use, even when experts resist

Reduce the translation burden. Hopper believed programming should not remain a specialist craft requiring people to translate every problem into low-level machine instructions. Her early compiler, A-0, assembled reusable code into programs, reducing repetitive handwork. Later versions moved toward more readable forms. A compiler is software that translates instructions written in a higher-level language into operations a computer can execute.

Shared language opened access. Hopper also advocated a common business language that could work across different machines. Her ideas helped shape the process that produced COBOL in 1959. It was verbose and not admired by every programmer, but businesses and government agencies could use it across hardware systems. The point was practical: accessible, portable tools could broaden who programmed computers and what those computers could do.

Analysis

Hopper’s approach treats ease of use as serious engineering, not cosmetic polish. A tool that requires fewer specialists can spread capability, but accessibility also redistributes authority: users gain some control over systems previously managed by experts. Standardization has costs, too. A common language may be less elegant than a specialized one, yet its value depends on shared adoption, not only technical beauty. The central design choice is what kind of capability a system makes possible for whom.

Watch professional standards turn open fields into closed clubs

A field changed its boundaries. In the 1960s, women may have made up 30 to 50 percent of programmers, but many were pushed toward lower-status work. At a 1968 NATO conference on the software crisis, no women were invited. The meeting promoted “software engineering,” a label that helped establish programming as a formal profession, while new credentials and hiring expectations narrowed the routes into it.

Exclusion had material costs. Women programmers were paid less than men doing comparable work, and employers often failed to accommodate childcare. The skills needed to understand clients and real-world problems were also discounted as soft or feminine. Evans argues that the industry sidelined people whose communication and coordination abilities could have helped solve the very software problems it was confronting.

Analysis

Professionalization can improve shared standards and accountability, yet it can also turn one historically contingent route into the definition of competence. The shift described here was not simply a change in vocabulary: it interacted with salaries, credentials, and who had access to mentorship. The caution is not to romanticize informal work, which can also conceal exploitation. It is to examine whether new standards measure the abilities a field needs or merely reproduce the status of people already inside it.

Treat software as a human artifact with a home address

A map preceded a game. Patricia Crowther helped survey Mammoth Cave, recording passages and turning field measurements into computer-generated maps with her husband, Will. After their marriage ended, Will used memories of the cave to write Adventure, an early text-based computer game. Players typed commands to move through descriptions of rooms and puzzles. Its virtual cave drew on a real place and on experiences the couple had mapped together.

Context changes what code means. Adventure spread through the ARPANET, the early research network, and helped establish a new kind of interactive play. Yet Patricia’s role in exploring and mapping the cave often disappeared from accounts of the game. The episode shows that software carries traces of its makers, relationships, and purposes. Understanding a program means asking not only how it works, but whose experience it represents.

Analysis

The cave story makes software feel less like an abstract product and more like a form of memory: a place translated into rules and descriptions that others can explore. That perspective complicates familiar authorship stories. A program may have one credited coder, yet depend on shared experience, data gathering, and earlier work that remains uncredited. Attribution should follow the chain of contribution, not stop at the person who typed the final lines.

Build technology around a community's actual unmet need

Start with a problem people recognize. In 1972, Pamela Hardt-English helped bring a donated mainframe to Project One, a San Francisco commune. Resource One first hoped to connect local Switchboards through a shared database, but the proposed terminals were costly and the system did not fit how those groups worked. The project found a more useful purpose in a Social Services Referral Directory.

Meet users where they are. The team gathered current information about services and sent it to agencies in printed binders, since social workers did not have convenient access to computer terminals. The directory connected people with shelters, support groups, and other services, and lasted for decades. Its success came not from forcing users onto new technology, but from adapting the technology to their practical needs.

Analysis

Resource One reveals that a digital system need not present itself as digital to create value. The database mattered because people could use its information, even when the interface was paper. This is a helpful correction to the assumption that innovation means more screens, more automation, or greater novelty. A project’s success should be measured by whether it improves the work users are trying to do, not by whether its most visible component looks futuristic.

Give networks librarians, registries, and rules that scale

Networks need caretakers. Elizabeth “Jake” Feinler ran the ARPANET’s Network Information Center, which documented its computers, people, and resources. Her team produced a handbook, maintained the host registry, and created WHOIS, a service that let users look up network contacts. They also helped establish familiar address categories such as .edu, .gov, and .com.

Invisible rules enable connection. Radia Perlman designed the spanning-tree protocol, a set of rules that gives data packets loop-free paths through Ethernet networks and finds new routes when connections fail. Her contribution differs from Jake’s, but both made a growing network manageable: one organized information about it, while the other helped data move through it. Networks depend on this unglamorous work as much as on cables and computers.

Analysis

These examples reveal two kinds of infrastructure that are easy to overlook: systems that direct information and systems that make information findable. A network can be physically connected yet practically unusable if people cannot locate resources or packets cannot travel reliably. The work also concentrates authority. Registries and naming rules decide what is legible and who can be found. Good infrastructure therefore needs both operational competence and careful attention to the people it makes visible.

Design online community as deliberately as its software

Connection takes more than access. Stacy Horn founded Echo, a New York bulletin board where people discussed culture, met in person, and built friendships. At its peak it had about 46,000 users. Horn made room for both public conversation and private groups, and ensured women held half of its conference-host roles. Those hosts welcomed newcomers, guided discussions, and enforced community rules.

Boundaries require judgment. Echo’s women-only conference, WIT, became the site of a difficult debate when a transgender woman sought access. Horn initially imposed a surgery requirement, then withdrew it; the community’s understanding changed through extended discussion. The conflict shows that creating an inclusive space is not a one-time technical decision. It requires listening, revising policies, and acknowledging that protection for one group can exclude another.

Analysis

Echo’s combination of social contact, private rooms, and active moderation anticipates a basic fact about community design: people do not speak identically in every setting. A public forum and a trusted small group serve different purposes. Yet moderation is never neutral by default. The WIT dispute shows how a rule meant to protect members can encode an assumption about who counts as a member. Inclusion depends on making those assumptions discussable and revisable.

A simpler web can beat richer systems through adoption

More powerful was not more popular. Wendy Hall’s Microcosm system linked information through a separate database called a linkbase. Its links could be updated and applied across documents, unlike Web links embedded in individual pages. Other researchers built systems for organizing ideas and connecting multimedia, with features that the early Web lacked.

Adoption changed the contest. At a 1991 conference, researchers saw the World Wide Web as technically limited. Its links were one-way and could break when pages moved. But the Web was free, relatively simple, and built on the expanding Internet. As more people used it, its value grew. The more sophisticated systems did not become the global standard. The Web’s reach made its limitations an acceptable tradeoff.

Analysis

The contrast between Microcosm and the Web is a reminder that technical merit is only one part of success. A system also needs a path to adoption, a community of users, and room to grow. Simplicity can be a strategic strength when it lowers the cost of participation. But popularity should not be confused with completeness: dead links and limited ways to organize knowledge remain real costs, even when a system has won.

Keep women's online spaces from becoming advertising funnels

Community and commerce pulled apart. Women’s WIRE began in 1993 as an online service for information, mutual support, and action. Users shared resources and organized a successful campaign urging the White House to change a health-care provision. When the service shifted toward the Web, it became women.com, a media company that sold advertising and attracted millions of monthly visits.

Growth changed the product. The move brought reach and revenue, but also pressure to offer conventional magazine content. Women.com increasingly resembled the mass-market women’s media it had once offered an alternative to. Meanwhile, independent projects such as Word, an early online magazine built around personal stories and playful web features, showed how the medium could support distinct voices. Commercial success can sustain a platform, but its incentives shape what survives.

Analysis

This history does not make commerce the villain or community automatically virtuous. Revenue can keep a service running, while unpaid ideals can leave its labor unsupported. The important question is what the business model rewards. When attention and advertising dominate, a platform may narrow its audience into predictable consumer categories. The challenge is to fund online spaces without quietly replacing their original purpose with whatever is easiest to sell.

Design for girls without pretending girlhood is one thing

Games shape first encounters. Brenda Laurel’s research found that many girls disliked games built around repeated failure and combat, and preferred exploration, character, and social choices. Her company, Purple Moon, created story games in which players guided Rockett through the social dilemmas of middle school. The games offered a chance to test decisions and imagine their consequences, rather than simply beat a level.

Representation can become a box. Purple Moon also built a community for players and tried to make online participation safer. Critics argued that games explicitly designed for girls could reduce girlhood to narrow stereotypes. The book places this debate alongside cyberfeminist efforts to claim digital space while recognizing that online life can reproduce sexism and other forms of exclusion. Better design invites more people in without deciding in advance what they must like.

Analysis

Purple Moon’s central insight is that design choices affect who feels invited to experiment with technology. Its limitation is equally instructive: research about a group can become a template that flattens differences within that group. A useful design response is not to ignore gender, since exclusion is real, but to avoid treating identity as a fixed preference. Variety, user feedback, and the freedom to choose different modes of play make inclusion more durable.

Analysis

Broad Band is a history of computing told through labor that conventional narratives often place at the margins. Its central argument is not simply that women contributed more than they have been credited for. It is that computing repeatedly depended on work categorized as secondary: calculation, programming, documentation, information organization, user support, community moderation, and cultural experimentation. When a new technology makes these tasks valuable, their workers can become central to the field, then lose status as the field professionalizes or commercializes.

The book’s strongest connective thread is usability. Lovelace imagines machines manipulating symbols; Hopper makes programming less dependent on machine-specific expertise; Feinler organizes a network so people can find their way through it; Horn designs social structures that help users speak; Laurel asks which games make girls want to play. These are not identical projects, but each treats technology as a relationship between a system and its users. A computer’s capabilities matter only when someone can access, understand, and put them to work.

The historical pattern also complicates the idea that innovation belongs to solitary visionaries. The ENIAC required a team to translate problems into operations. The Internet required both routing protocols and human registries. Online communities depended on hosts, rules, and shared habits. Even a celebrated game could rest on an overlooked collaborator’s maps and experience. In this account, invention is often distributed across people and activities that later histories divide into separate categories.

A useful caution is that recovering women’s work should not turn women into a single explanatory category. The stories show varied expertise and disagreement, from engineering to entrepreneurship, community work, art, and scholarship. Nor does attention to women alone explain every exclusion shaped by race, class, or access. The book’s lasting challenge is therefore broader: examine who performs the work, who receives credit, who controls the tools, and whose needs the resulting technology serves. That audit can change how both history and new systems are built.

Summary in 30 Seconds
Computing has always relied on people who translate problems, document systems, organize information, and help users make technology work. Women performed much of this labor, yet often received less credit and status as programming became a formal profession. Practical tools and networks succeed when they fit users' needs, while online communities depend on thoughtful rules and moderation. Commercial growth can expand a platform while shifting its priorities.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.93 out of 5
Average of 2k+ ratings from Goodreads and Amazon.

Broad Band receives mostly positive reviews for its informative exploration of women's contributions to computing and internet history. Readers appreciate learning about overlooked pioneers like Grace Hopper and Jake Feinler. The book is praised for its engaging writing style and thorough research. Some criticize the later chapters as weaker or dated. A few reviewers found the writing dry or disliked the political perspective. Overall, most readers found the book eye-opening and valuable for highlighting women's central role in technological development.

Your rating:
4.44
120 ratings
Want to read the full book?

Glossary

Kilogirl

A measure of computing labor

A unit used by mid-twentieth-century researchers to estimate roughly a thousand hours of human computing work. The term treated groups of women performing calculations as a comparable measure of machine labor. Its history captures both the scale of collective human computation and the gendered assumptions embedded in early technical language.

Automatic programming

Software that assembles programs

Grace Hopper’s broad aim of reducing the need to write machine-level instructions by hand. Her early compilers assembled tested, reusable code and translated it into instructions a computer could execute. The goal was to make programming more efficient, portable across machines, and accessible to people beyond a small expert class.

COBOL

A shared business language

The Common Business-Oriented Language, developed in 1959 through a collaboration among government, industry, and programmers. It was designed for business data processing and to work across different computers. Its readable, word-based style helped its spread, although its verbosity and longevity also made it a frequent target of programmers’ criticism.

ARPANET

An early research network

A U.S. government-funded network connecting research and military computers beginning in the late 1960s. It used packet switching, sending data in pieces that could travel across different routes and be reassembled at their destination. Its infrastructure and practices helped establish the foundations of the Internet.

WHOIS

A network lookup service

A service created at the ARPANET’s Network Information Center to let users look up information about people and network resources. The original system helped users identify contacts and affiliations across a growing network. WHOIS continues in evolved form as a way to look up information associated with Internet domains and services.

spanning-tree protocol

A loop-free network routing method

A protocol designed by Radia Perlman to organize paths through Ethernet networks. It creates a loop-free structure connecting network devices, preventing data from circulating endlessly. If a connection fails, the system can determine an alternative route. This made Ethernet more reliable and capable of supporting larger networks.

Hypertext

Linked, navigable information

A way of structuring information so that documents or ideas connect through links, allowing readers to move among related material rather than follow one fixed sequence. Before the World Wide Web, researchers developed hypertext systems for browsing multimedia, organizing knowledge, and creating associative paths that users could build and share.

Microcosm

A flexible hypertext system

A hypertext system developed by Wendy Hall and colleagues at the University of Southampton. Rather than embedding every link inside a document, Microcosm stored links separately in a linkbase. This allowed links to be updated, applied across documents, and tailored to different users and collections of information.

Community Memory

A public electronic bulletin board

An early public-access computer system launched in Berkeley in 1973. A terminal in a local record store connected users to a shared database where they could post questions, information, and classified-style messages. Its uses ranged from finding local services to trading jokes, demonstrating how networked computers could support community life.

Cyberfeminism

Feminist work in digital culture

A varied 1990s movement of artists, writers, and technologists who explored gender, sexuality, and power in digital networks. Cyberfeminists used online spaces and media art to challenge male control of technology and imagine new forms of expression. The movement did not have one fixed definition, and its early optimism met persistent digital sexism and commercialization.

FAQ

What's Broad Band: The Untold Story of the Women Who Made the Internet about?

  • Focus on Women in Tech: The book highlights the significant contributions of women in the development of computing and the Internet, often overlooked in a male-dominated field.
  • Historical Context: It provides a historical narrative from the 19th century to the rise of the Internet, intertwining personal stories with technological advancements.
  • Cultural Impact: The book explores the cultural implications of technology, emphasizing the need to include women's narratives in the history of technology.

Why should I read Broad Band?

  • Inspiring Stories: It offers motivational accounts of women who broke barriers in technology, serving as powerful examples of resilience and creativity.
  • Educational Value: Readers gain a deeper understanding of the history of computing and the Internet, learning about key figures and events.
  • Cultural Relevance: The book provides critical insights into diversity and inclusion in tech, encouraging recognition of women's contributions.

What are the key takeaways of Broad Band?

  • Women’s Central Role: Women have always been central to computing, contributing significantly in areas like programming and networking.
  • Historical Revisionism: The book advocates for revising the historical narrative to include women's stories, essential for understanding technology's evolution.
  • Interconnectedness of Technology and Society: It highlights how technological advancements are deeply intertwined with social changes, emphasizing the human element.

What are the best quotes from Broad Band and what do they mean?

  • “Female mental labor was the original information technology.”: This quote underscores the foundational role women played in early computing, challenging the notion that technology is solely a male domain.
  • “Computers are built to be turned on, cables are meant to be patched in, and links are made to be clicked.”: It reflects the idea that technology is inherently social, requiring human interaction to function.
  • “Women turn up at the beginning of every important wave in technology.”: This statement highlights the consistent presence of women in technological advancements, calling for recognition of their contributions.

Who are some key figures mentioned in Broad Band?

  • Ada Lovelace: Considered the first computer programmer, her work on the Analytical Engine laid the groundwork for modern computing.
  • Grace Hopper: A pioneering computer scientist, she developed the first compiler and was instrumental in the development of COBOL.
  • The ENIAC Six: This group of women programmers worked on one of the first electronic computers, illustrating the critical role women played in early computing.

How does Broad Band address the issue of gender in technology?

  • Highlighting Inequities: The book discusses systemic inequities faced by women in tech, including wage disparities and lack of recognition.
  • Celebrating Contributions: It emphasizes the importance of celebrating women’s contributions, advocating for their recognition in the historical narrative.
  • Call to Action: The book encourages the tech industry to address gender disparities and create a more inclusive environment.

What is the significance of the term "kilogirls" in Broad Band?

  • Historical Context: "Kilogirls" refers to early female programmers who performed complex calculations, highlighting their collective effort.
  • Measurement of Labor: It serves as a metaphor for measuring women's contributions in computing, akin to quantifying computing labor.
  • Cultural Recognition: The term seeks to reclaim and celebrate women's contributions, challenging the historical narrative that overlooks their roles.

What role did community play in the development of technology, as discussed in Broad Band?

  • Building Networks: Women created and participated in communities that fostered collaboration and innovation in technology.
  • Support Systems: Community provided support for women, helping them navigate challenges and build their careers in a male-dominated field.
  • Cultural Impact: The communal aspect of technology development is highlighted as a driving force behind many innovations.

How does Broad Band connect the history of women in technology to modern issues?

  • Continuity of Struggles: The book draws parallels between historical struggles and contemporary gender inequality in tech.
  • Inspiration for Change: Showcasing past achievements, it serves as inspiration for promoting diversity and inclusion in technology today.
  • Cultural Relevance: It emphasizes the ongoing relevance of women’s contributions in today’s digital landscape.

What is the significance of Echo in Broad Band?

  • Community Hub: Echo was a vital online community where users, particularly women, could connect and share ideas.
  • Cultural Events: It hosted cultural events that fostered a sense of belonging among users, innovative for its time.
  • Real-World Connections: Echo emphasized face-to-face interactions alongside online communication, relevant to today’s social media.

What challenges do women face in the tech industry today, as discussed in Broad Band?

  • Gender Bias: The book addresses ongoing gender bias in hiring and promotion, rooted in cultural stereotypes and systemic inequalities.
  • Lack of Representation: It highlights the lack of female representation in leadership positions, perpetuating exclusion.
  • Workplace Culture: Discusses how unwelcoming workplace cultures can lead to feelings of isolation and discouragement for women.

How does Broad Band envision the future of women in technology?

  • Empowerment through Knowledge: Emphasizes education and mentorship in empowering women to pursue tech careers.
  • Advocacy for Change: Calls for collective action to address gender disparities, promoting inclusivity in tech.
  • Celebration of Diversity: Envisions a future where diverse voices are celebrated, leading to more innovative technologies.

About the Author

Claire L. Evans is a journalist, musician, and author known for her work exploring technology and culture. She is a founding editor of VICE's science and technology publication Motherboard and has written for various outlets including The Guardian and Wired. Evans is also a musician, performing in the pop duo YACHT. Her background in both technology journalism and artistic pursuits informs her approach to writing about the history of computing. Evans conducted extensive research and interviews for Broad Band, aiming to bring attention to overlooked women in tech history.

Download PDF

To save this Broad Band summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.47 MB     Pages: 23

Download EPUB

To read this Broad Band 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.49 MB     Pages: 27
Want to read the full book?
Follow
Listen
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 24,
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...