openmargin
A social reading app built around shared ebook margins ran into slow shipping, DRM and content-access limits, and weak adoption despite public interest.
View original storyProduct snapshot
What it was
Added shared annotations and discussion to ebooks, initially around iPad reading.
Who it was for
Problem / value
Help readers discuss passages and meet others reading the same books.
What happened
Summary
openmargin built a social reading layer for ebooks, but weak adoption, slow shipping, and ebook ecosystem constraints kept it from reaching its potential.
Outcome
Did not live up to its potential after weak adoption and platform constraints.
Demand signal
The evidence points less to generic no-demand and more to weak adoption in a platform-constrained market where readers had to share the same books and import compatible files.
Distribution issue
Amazon’s ebook dominance, DRM, and the need for compatible ePub imports constrained both acquisition and product usefulness.
Timeline
- Started as a university graduation project in 2009.
- Raised EUR 130,000 in subsidies.
- Launched publicly at The Next Web in Amsterdam in 2011.
- Founder later described years without real traction.
Before you build
Why it matters
openmargin shows that shared annotation only works when users can easily access the same content and have enough reason to return around that shared object.
Primary check
Validate content access, import friction, and a dense repeat-reading loop before building social features around controlled media.
If you build this today
Start with one reachable reading group, one book format, and one repeated discussion use case before investing in broad social-reader infrastructure.