The document discusses the "Book as a Service" approach to retailing books in the future. Key aspects of this approach include: 1) Hosting books on the cloud to allow for multi-device synchronization, real-time learning and control, and mutable digital artifacts. 2) Enabling social reading features that break down walls between books, readers, and authors. 3) Aggregating content to serve as a hub for readers, publishers, and authors. 4) Providing API access to books hosted on the cloud.

1. The future is a cloud hosted retail store
The “Book as a Service” approach
Justo Hidalgo, Chief Product Officer
@justohidalgo

3. and that used to be fine

4. until something happened

6. We live in a world where
everything can be copied

7. We live in a world where
people can publish content
for free

8. Rules are broken

9. Will people pay for your
content?

10. NO
(sorry)

11. unless

12. Extremely high quality and
differentiated content
Impressive brand recognition

13. Total availability

14. Tough, huh?
?

15. Classic content-focused business
model

16. Content is not enough
FREE CONTENT PAID
CONTENT
many
1

17. But it is still key…

18. … and core of your business

19. I (and some others ) have the
solution
c

20. Freemium
READERS FREE ACCESS WANT MORE?
TO CONTENT
c

21. Not enough!!!

22. Let me repeat again

23. Content is NOT enough
FREE CONTENT PAID
CONTENT
many
1

24. BOOK AS A SERVICE
API

25. 1. Book on the cloud

26. 1.a. Multidevice synchronization
HTML5 Web iPad app

27. 1.b. Real-
Time
Learning
and
Control

28. 1.c. Mutable artifact
Credits: Craig Mod, June 2011

29. 2. Social Reading

30. Breaking
the wall
between
the book
and the
readers…

31. … among the readers themselves…

32. … and with the authors?

33. 3. Content aggregation

34. This is what many of you would like
to have (picture of Apple Store in NYC)

35. But that’s a huge challenge for
MOST publishers… and for readers
Big Publisher
I just wanted
to read a
book…
Great Publisher
Cool Publisher

36. “Book as a Service” provides a real
HUB for readers, publishers and
authors

37. 4. API access
API

38. Are books “it”?

41. The “book” will
always be a true and
reliable representation
of our stories,
experiences and
knowledge

42. BOOK AS A SERVICE
API

44. Thanks
Justo Hidalgo
jhidalgo@24symbols.com
@justohidalgo
www.24symbols.com
@24symbols