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
Working in Public

Working in Public

The Making and Maintenance of Open Source Software
Millions use your code; who pays for the work that keeps it dependable?
by Nadia Eghbal 2020 252 pages
3.92
500+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

GitHub lowered the barrier to publishing, then raised the cost of attention.

Convenience changed the workflow. Before GitHub, developers often found code on separate websites and coordinated through mailing lists, each project with its own customs. Git and GitHub made it easier to publish, discover, and propose changes through a shared interface. By 2017, GitHub hosted 25 million public projects, and its user base kept growing. One click could now bring a stranger into a project’s issue tracker or pull request queue.

Reach brought a trade-off. GitHub made open source more accessible, but that accessibility also increased the volume of requests landing on maintainers. The platform’s success did not simply create more collaboration. It made more people visible to one another, while leaving the human work of reading, answering, and reviewing largely unchanged.

Analysis

This is a classic infrastructure trade-off: reducing the cost of entry can increase demand faster than the system’s capacity to serve it. Similar dynamics appear in public transit and customer support, where easier access is a genuine benefit until queues become unmanageable. The lesson is not that access should be restored to its old, inconvenient state. It is that platforms must treat attention as part of their infrastructure, rather than assuming that smoother participation is free.

Keep code public without making every decision participatory.

Access is not membership. Open source usually lets anyone read, download, and reuse code. It does not mean every user can approve changes or direct a project. On GitHub, people can propose edits, but maintainers decide which ones to accept. The distinction matters because users may want a working tool without wanting to join its development or learn its local norms.

More discussion can become a burden. Python’s long debate over a proposed syntax change attracted sprawling comment threads, including input from people with little context. Guido van Rossum, Python’s creator, stepped down as its long-time decision leader after 27 years. The episode shows that public deliberation can remain open in principle while still needing limits on where and how participation occurs.

Analysis

The distinction resembles the difference between transparency and direct democracy. Public records let people observe decisions; they do not require every decision to be made by a mass vote. That separation can preserve accountability while allowing people with context and responsibility to act. The difficulty is legitimacy: restrictions on participation need clear explanations and fair procedures, or they can look like arbitrary exclusion. Openness is most durable when its boundaries are explicit.

A thousand contributors can still leave one maintainer doing the work.

Counts conceal concentration. A study of 275 popular GitHub projects found that nearly half of contributors participated only once. Together, those one-time contributors accounted for less than 2 percent of commits. Another study found that in more than 85 percent of examined projects, fewer than 5 percent of developers were responsible for more than 95 percent of code and social activity.

A contribution is not a commitment. Many casual contributors are users who submit a fix for their own problem and then move on. Their work can be useful, but it does not automatically create a durable team. Bootstrap illustrates the imbalance: in 2017, three developers authored over 73 percent of its commits, despite the framework’s widespread use.

Analysis

The pattern resembles the difference between a crowd and an organization. A crowd can produce bursts of useful activity, but an organization needs continuity, shared knowledge, and people willing to handle unglamorous responsibilities. Treating every one-time participant as future capacity leads to unrealistic staffing assumptions. Still, concentrated work is not automatically unhealthy: a small, skilled team may be more effective than a large group with high coordination costs. The key question is whether the essential work has dependable owners.

Choose governance by project shape, not by open-source mythology.

Four patterns clarify the choices. The book classifies projects by user growth and contributor growth. Federations have many users and many contributors, as with Linux. Clubs have fewer users but an engaged contributor group. Toys have little growth on either side and often remain personal experiments. Stadiums attract many users while relying on only a few regular contributors, as many popular libraries do.

Different shapes need different care. Federations may need working groups and formal decision processes. Clubs depend on sustained participation among a small group. Stadiums need ways to protect maintainers from overwhelming support demands. A project’s likely shape depends partly on its size, technical scope, support burden, ease of contribution, and audience.

Analysis

The framework is useful because it replaces one idealized picture of open source with several workable organizational forms. In ecology, a healthy system is not defined by every species multiplying equally; roles and population sizes vary with the environment. The same applies here. The categories are best used as diagnostic tools, not fixed identities. A project can change shape as it grows, and a governance model that once fit may become costly or ineffective under new conditions.

Treat maintenance as ongoing infrastructure, not a finished product.

Working software keeps changing. Code may be cheap to copy, but code that people rely on needs updates, security fixes, documentation, and compatibility with other tools. The book distinguishes code in a static state, available to inspect or download, from code in an active state, running in systems that depend on it. The second state brings ongoing responsibilities.

The burden is substantial. A 2018 Stripe study estimated that developers spend 42 percent of their time maintaining code. Older technologies can persist for decades because replacing them may be riskier than keeping them running. Even a small library can become an important link in a larger chain: when the 17-line JavaScript package left-pad disappeared, dependent software broke until the package was restored.

Analysis

This is a lifecycle-cost argument, not merely a plea to appreciate developers. Infrastructure is valuable partly because it continues to work, but continued operation requires labor that is easy to overlook precisely when it succeeds. The analogy also exposes a planning gap: organizations often budget for launch and feature development more readily than for upkeep. Yet maintenance is not always the right choice. A stable project may need little attention, while an obsolete tool may be better replaced than preserved indefinitely.

Judge project health by work handled, not contributor totals.

Three measures tell different stories. A project may be popular, meaning many people use it; depended upon, meaning other software relies on it; or active, meaning development and maintenance continue. These qualities do not always coincide. A widely used project might be inactive, while a stable tool may need few new commits and still serve users well.

Raw totals can mislead. The bus factor estimates how many key people would have to disappear before a project is in trouble. It is a useful warning, but contributor counts alone can hide who holds the knowledge. A better picture includes work volume, unanswered issues, review delays, and the difficulty of replacing the software. Even these measures need context: a long-open discussion is not equivalent to a neglected security fix.

Analysis

This resembles reliability engineering, where system health is inferred from failure rates, response times, and dependencies, not from the number of employees assigned to a service. The shift from counting people to tracking work makes comparisons more meaningful across different project types. Metrics still need interpretation. A quiet repository can signal abandonment, or simply mature code that rarely needs changing. Good evaluation combines observable activity with knowledge of the project’s role and replacement options.

Protect scarce attention with filters, automation, and peer support.

Reduce avoidable requests. Maintainers use issue templates, tests, bots, and clear documentation to help people submit useful reports and changes. Among the top 100 projects ranked by issue volume in one analysis, 93 percent used issue templates. For the popular video-downloading tool youtube-dl, maintainers said templates helped screen out reports that lacked the information needed to reproduce a problem.

Let users help users. Support forums and question-and-answer sites can move routine questions away from maintainers. In an analysis of 100 high-issue-volume projects, 89 percent used at least one support channel beyond GitHub issues. These systems take work to set up, but they can keep common questions from repeatedly consuming the attention needed for code, reviews, and difficult bugs.

Analysis

This is queue management applied to software work. Templates improve the quality of incoming requests; peer support increases the number of people able to resolve routine problems. Both can raise the system’s effective capacity without requiring maintainers to personally answer every question. Automation is not neutral, however. A rigid form can deter legitimate reports, and a community answer can be wrong or outdated. Strong systems make the desired path clear while leaving room for escalation and correction.

Fund maintenance and stewardship, not a flood of beginner pull requests.

Pay for neglected work. New contributors may enjoy writing a feature, but they are not necessarily eager to review changes, triage issues, or manage releases. Paying for every contribution can also reward activity that creates more review work than value. The book points to Hacktoberfest, which offered a T-shirt for a set number of pull requests, as an incentive that could produce low-quality submissions rather than lasting maintenance.

Target persistent needs. Django’s paid Fellowship program hired someone to handle patch review, issue triage, and release work. It improved response times and helped keep releases on schedule. Companies may fund reliability or technical support, while individuals may support developers directly. The right choice depends on which work is missing and who benefits from it.

Analysis

The distinction is between rewarding visible output and financing essential capacity. Incentive design often fails when it pays for what is easy to count instead of what an organization needs. A pull request is visible; accumulated maintenance knowledge is less so. Funding should therefore follow the project’s actual bottlenecks. It should also avoid assuming that money always improves motivation: it can support necessary work, but poorly targeted rewards can crowd out intrinsic interest or add another layer of administration.

Charge for scarce maintainer attention, not reusable code.

Copying and responding differ. A person can download the same code as thousands of others at little additional cost to its creator. A maintainer’s time is different: answering a question, reviewing a change, or providing urgent support consumes limited attention. The book argues that open source can remain freely available while some forms of access to its producers carry a price.

Different buyers value different things. Companies may pay for dependable support, influence over a roadmap, or a direct relationship with a maintainer. Individual users may support a developer because they value that person’s work and want to encourage more of it. Sponsorships and subscriptions can therefore fund continued production without putting the code itself behind a paywall.

Analysis

This reframes the economic problem from selling copies to allocating scarce service. It is similar to the distinction between a freely available public resource and a limited professional service attached to it. The approach can align payment with actual demand, but it needs safeguards. If paying buys excessive influence over project decisions, community trust can erode. Clear separation between support, sponsorship, and governance helps keep financial access from quietly becoming control.

Build a loyal audience before chasing internet-scale reach.

Attention is not the same as support. A viral post or widely downloaded library can attract an enormous audience without creating a durable relationship with its creator. The book describes a shift toward creators building smaller, more committed audiences through newsletters, subscriptions, sponsorships, and other recurring support. These models reward people who repeatedly deliver something a particular audience values, rather than merely accumulating views.

Creators need boundaries, too. Large public platforms make broadcasting easy but can turn every reply, question, and message into another claim on the creator’s time. Newsletters, podcasts, private groups, and moderated spaces offer different balances between reach and interaction. The aim is not to make every audience member a participant. It is to sustain meaningful work without making constant availability the price of visibility.

Analysis

The creator economy is often measured by reach because views are easy to count. But recurring support depends more on relevance, trust, and a credible promise of future value. This can make niche audiences economically powerful without requiring mass popularity. The model is not equally available to everyone: reputation, time, geography, and platform access shape who can convert attention into income. Still, it offers a useful alternative to treating exposure as a sufficient reward for ongoing labor.

Analysis

The book’s central move is to separate two things that are often treated as one: access to a digital product and access to the people who maintain it. Open source code can circulate widely at low cost, but decisions, review, support, and upkeep rely on finite human attention. This distinction explains why greater participation can worsen the conditions of production even while access to the product remains socially valuable.

The account also revises the familiar story of open source as a community effort. Some projects do operate through durable, many-to-many collaboration. Many others resemble creators with large audiences: a small number of people make decisions while a much larger group consumes the result. That is not necessarily a failure of community. It is a different organizational form, with different requirements for governance, support, and funding.

The framework is strongest when it treats project types as varied and measures health through work, dependencies, and resilience rather than a single participation metric. Its wider implication is that platforms are not neutral containers. Their interfaces lower some costs while generating new expectations about responsiveness, visibility, and access. Any sustainable design must account for those expectations, not just the cost of hosting code.

A useful caution is that attention cannot be treated as a simple commodity. Who gets heard, whose requests are screened out, and who can afford paid access are governance choices with unequal consequences. Boundaries protect maintainers, but badly designed boundaries can also exclude valuable contributors or shield poor decisions. The practical challenge is therefore not to maximize participation or suppress it, but to make responsibility, authority, and support proportionate to a project’s actual structure. That is a more realistic standard for open collaboration than assuming that every public resource should be run as a permanent town meeting.

Summary in 30 Seconds
Public code is easy to copy, but support, review, and upkeep consume scarce human attention. In more than 85 percent of studied projects, fewer than 5 percent of developers handled over 95 percent of code and social activity. Match governance to a project's users and contributors, and judge its health by work handled, dependencies, and resilience. Templates, automation, peer support, and targeted funding help sustain maintenance without restricting access to the code.
Contains spoilers

Last updated:

Report Issue

Review Summary

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

Working in Public explores the dynamics of open-source software development, focusing on maintainer challenges, community structures, and economic models. Eghbal's insights on project management, contributor relationships, and funding mechanisms are praised for their depth and relevance. While some readers found the book disorganized or lacking novel information for experienced developers, many appreciated its analysis of open-source culture and its implications for online communities. The book's beautiful physical design and accessibility to non-technical readers were also commended.

Your rating:
4.46
188 ratings
Want to read the full book?

Glossary

Commons-based peer production

Self-organized collaborative production

A way of producing shared resources through voluntary, distributed participation rather than through a company or market contract. In open source, developers select tasks that interest them and coordinate contributions without a central employer assigning the work. The model works best when tasks can be divided into manageable pieces and the cost of coordinating them remains low.

Federations

Many users, many contributors

One of the book’s four open source production models. Federations have both substantial user growth and substantial contributor growth. Because their work and decisions are distributed across many people, they often develop formal processes, working groups, leadership roles, or proposal systems to coordinate contributors and represent the broader user base.

Clubs

Niche users who contribute

One of the book’s four open source production models. Clubs have relatively low user growth but high contributor growth, so users and contributors substantially overlap. Their narrow focus can create strong member commitment and high retention, even when the project is not widely used across the software world.

Toys

Small personal projects

One of the book’s four open source production models. Toys have low user growth and low contributor growth. They are often experiments or side projects that their creators maintain for personal interest, without expecting large audiences, sustained outside contributions, or extensive organizational structure.

Stadiums

Many users, few maintainers

One of the book’s four open source production models. Stadiums have high user growth but low contributor growth, leaving one or a few maintainers responsible for most decisions and ongoing work. Their central challenge is managing a large audience without assuming that audience members will become long-term collaborators.

One-way mirror

Public viewing, limited participation

A proposed way to organize public work so people can inspect code and observe discussions without automatically gaining access to producers’ attention. Users can read, download, and learn from the work, while participation in decisions or requests may require approval or other boundaries. The goal is to preserve transparency without making every interaction obligatory.

Extractive contributions

Requests costing more than they add

Contributions or interactions whose cost to review, coordinate, or maintain exceeds their likely benefit to the project. They can include questions, feature requests, event proposals, or code changes, and may come from well-meaning users or experienced contributors. The category concerns the net effect on producers’ limited attention, not the contributor’s intentions.

Static state

Code as a copyable artifact

The condition in which code can be viewed, downloaded, or shared as a fixed body of information. In this state, additional copies generally cost little and do not require active involvement from the maintainer. The code may be useful as a reference or historical artifact, whether or not it is currently running in production.

Active state

Code running within dependencies

The condition in which code is used by software or systems that depend on it. Active code can require updates, compatibility work, security fixes, user support, and coordination with other components. Its costs arise not from copying the code but from keeping it useful and reliable as its environment changes.

Status as a Service (StaaS)

Platforms that distribute social status

A description of platforms whose value includes helping users gain visible recognition, prestige, or social capital. For creators, status can attract attention and support, but it also creates expectations of continued output. A creator’s reputation is therefore not only a reward for past work; it can become an asset that requires ongoing maintenance.

FAQ

What is Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal about?

  • Focus on open source maintenance: The book examines how open source software is created and, more importantly, maintained, highlighting the often invisible labor of maintainers.
  • Platform and community evolution: It explores how platforms like GitHub have transformed open source from collaborative communities to projects centered around individual maintainers.
  • Economic and social dynamics: Eghbal discusses the paradox of open source’s immense value versus the lack of financial and social support for its creators.
  • Broader digital implications: The book draws parallels between open source and other online creator economies, offering insights into digital collaboration and content production.

Why should I read Working in Public by Nadia Eghbal?

  • Unseen labor revealed: The book uncovers the hidden work and challenges behind the open source software that powers much of the internet.
  • Understanding sustainability: It provides a nuanced look at why many open source projects struggle with sustainability and maintainer burnout.
  • Practical frameworks: Eghbal offers frameworks for measuring software value, managing contributor attention, and understanding funding models.
  • Broader relevance: The lessons extend to anyone interested in digital culture, platform dynamics, and the future of collaborative production.

What are the key takeaways from Working in Public by Nadia Eghbal?

  • Shift to solo maintainers: Most open source projects are now maintained by a few individuals, challenging the traditional model of large, collaborative communities.
  • Maintainer attention is scarce: The real bottleneck in open source is not code, but the limited attention and energy of maintainers.
  • Platforms shape behavior: Tools like GitHub have centralized development, making contribution easier but also increasing noise and maintainer workload.
  • Maintenance is undervalued: Ongoing support, infrastructure, and user management are costly and often go unrecognized or unrewarded.

What are the main concepts and frameworks introduced in Working in Public by Nadia Eghbal?

  • Software as public infrastructure: Open source code is likened to public infrastructure, with value derived from its use and dependencies.
  • Dual economic goods: The book distinguishes between software as a public good (consumption) and as a commons (production), where maintainer attention is rivalrous.
  • Maintainer attention as currency: Attention is the limiting resource in open source, and managing it is crucial for project health.
  • Reputation and funding: The reputation of maintainers often drives funding and support more than the code itself.

How does Nadia Eghbal define the roles of maintainers, contributors, and users in open source projects?

  • Maintainers: Stewards responsible for the project’s direction, governance, and ongoing health, often handling triage, code review, and decision-making.
  • Contributors: Individuals who make code or non-code contributions, ranging from one-time participants to regular, active members.
  • Users: Primarily consumers of the code who may offer feedback or bug reports but usually remain outside the core contributor community.
  • Role distinctions matter: Understanding these roles helps clarify project dynamics and the distribution of labor and responsibility.

What are the four types of open source project models described in Working in Public by Nadia Eghbal?

  • Federations: Decentralized projects with high user and contributor growth, formal governance, and working groups (e.g., Linux, Rust).
  • Clubs: Projects with high contributor but low user growth, featuring tight-knit, dedicated communities (e.g., Clojure).
  • Toys: Small, personal, or experimental projects with minimal users and contributors, often maintained by a single person.
  • Stadiums: Projects with high user but low contributor growth, maintained by a few individuals with many casual contributors (e.g., Babel, webpack).

How has GitHub changed the culture and workflow of open source development according to Nadia Eghbal?

  • Standardization and convenience: GitHub unified tools and workflows, making it easier to discover, share, and contribute to projects.
  • Shift in values: Modern developers prioritize ease of use and visibility over ideological concerns about code freedom.
  • Platform dependency: Developers increasingly rely on GitHub’s infrastructure and social features, creating new challenges for maintainers.
  • Increased participation and noise: Lower barriers to entry have led to more casual contributors, often overwhelming maintainers with low-quality or infrequent contributions.

What are the hidden costs of maintaining open source software according to Working in Public by Nadia Eghbal?

  • User support burden: Maintainers spend significant time addressing help requests, bug reports, and feature demands.
  • Technical debt and refactoring: Ongoing maintenance includes cleaning up code, testing, and managing infrastructure, which is often unrewarding.
  • Dependency management: Projects rely on many external packages, requiring constant updates and vigilance for security.
  • Infrastructure and moderation: Hosting, security, and community moderation add real costs, even if code distribution is free.

How does Working in Public by Nadia Eghbal explain the decline of large-scale collaborative open source communities?

  • Context collapse: Platforms like GitHub merge distinct communities, eroding collective identity and making social norms harder to enforce.
  • Overwhelming participation: The influx of casual contributors increases noise and workload for maintainers.
  • Centralized governance: Many projects now revolve around a few maintainers rather than decentralized collectives.
  • Complex governance challenges: Defining membership, enforcing conduct, and balancing authority have become more difficult.

What strategies and advice does Nadia Eghbal offer for open source maintainers managing contributor communities?

  • Balance reactive and proactive work: Maintainers must juggle user interactions with coding and project vision.
  • Recognize contributor diversity: Tailoring support to casual versus active contributors improves engagement and sustainability.
  • Leverage automation and community support: Tools like bots and user-to-user support can reduce workload and filter noise.
  • Set boundaries: Limiting participation or closing issues can help maintainers preserve their attention and well-being.

How does Working in Public by Nadia Eghbal address funding models and economic dynamics for open source developers?

  • Institutional vs. individual funding: Companies fund for code quality and influence, while individuals sponsor maintainers for reputation and ongoing work.
  • Attention as currency: Money can make maintainer attention excludable, through paid support or sponsorships.
  • Funding maintainers over casual contributors: The book argues for prioritizing support for those who bear the bulk of maintenance work.
  • Project vs. individual funding: Funding individuals aligns with open source’s distributed nature, while project funding requires more formal governance.

What are the best quotes from Working in Public by Nadia Eghbal and what do they mean?

  • “Nobody can keep open house in a great city.” — Jane Jacobs: Highlights the difficulty of managing open, public resources without clear boundaries and governance.
  • “Information wants to be free. Information also wants to be expensive.” — Stewart Brand: Captures the tension between free distribution and the need for creator compensation in digital goods.
  • “Open source code is a form of public infrastructure that requires maintenance.” — Nadia Eghbal: Frames open source as essential infrastructure, emphasizing the need for ongoing care and funding.
  • “The production of open source software functions more like a commons—where attention is the rivalrous resource.” — Nadia Eghbal: Stresses that while code is freely consumed, maintainer attention is limited and must be managed carefully.

About the Author

Nadia Eghbal is a researcher and writer specializing in open-source software and digital infrastructure. She gained prominence through her work at GitHub, where she served as a senior developer-relations researcher. Eghbal's expertise in the open-source ecosystem is evident in her thorough analysis of its history, economics, and social dynamics. Her writing style is praised for its clarity and accessibility to both technical and non-technical audiences. Eghbal's work extends beyond open source, drawing parallels to broader trends in online communities and the creator economy. Her insights have made her a respected voice in discussions about the future of digital collaboration and sustainability.

Download PDF

To save this Working in Public summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.42 MB     Pages: 22

Download EPUB

To read this Working in Public 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.39 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...