Entries tagged with “ereader” from Tools of Change for Publishing
800 Newspapers Coming to Iliad E-Reader
Peter Brantley
December 6, 2008
| Permalink
| Comments (3)
|
Listen 
iRex Technologies scores scores of newspapers for its new iLiad e-reader. From E-Reads:
Digitally delivered news is gaining momentum and as we turn the corner to 2009 it's gotten a rocket boost from the Dutch firm iRex Technologies, which announced it has made a deal with NewspaperDirect to deliver 800 newspapers on iRex's Digital Reader 1000 ...
The iRex/NewspaperDirect partnership will undoubtedly cause some headaches for Amazon.com, too. A visit to Amazon's Kindle newspaper web page shows 28 listings. The 800 titles to be carried on the iRex 1000, dubbed 'Kindle Killer' by some, will obviously dwarf Kindle's offering. Of course, many of them are foreign language papers like Le Figaro and Die Welt. But 800 is 800 and that's good news for the environment.
Q&A With Co-Creator of Classics iPhone E-Reader
Mac Slocum
November 26, 2008
| Permalink
| Comments (3)
|
Listen
We've covered iPhone-based e-readers in the past, but the Classics application offers a few twists: it's not free, and the app's book content is updated along with the software itself. Classics co-creator Phill Ryu discusses the application's design and development in the following Q&A.
Why did you develop a book-centric application?
When we started comparing the iPhone to the Kindle, it was immediately clear to us that we could take advantage of the iPhone's brilliant color screen and touch capabilities to create a reading experience that would stand out from the crowd, so it began as a very, very tempting challenge almost, and eventually turned into a months-long passion project.
How many books do you offer?
We're currently offering a dozen books. They're handpicked favorites of ours, but we'll be adding more with free updates to the app.
Are these books all in the public domain?
Yeah, they are public domain. At the start, [co-creator Andrew] Kaz and I thought we could really do something radical in terms of the digital reading experience, but we couldn't start working with publishers based on the strength of some cool interface ideas, so we settled with the "Classics" name and created this as essentially the first prototype of our reading engine.
Did you consider releasing this application for free?
Yes, for a moment. Then someone knocked on my apartment door and slipped in a rent payment notice letter. The reality of the situation was, we had gone basically broke over the summer working on a pretty cool desktop app, and had to halt development on that until we could find some income. At that point, we came up with the brilliant plan to develop an iPhone app in a few weeks to generate some income, to continue the aforementioned desktop app. Classics of course ended up turning into a serious passion project lasting months of development time, and we went extra broke due to it, so going free was hardly an option. We're rather painfully aware that free apps tend to gather something like 25-50 times the downloads of similarly charting paid apps, and we'd like to reach that audience someday, but most likely it'll be with a spinoff app, and not with Classics.
Are you still developing the desktop app? Does this app also focus on books/content?
I really can't (and shouldn't) talk details, because the app might never fly depending on how talks with some content publishers go, but no, it's not book related.
You're using Apple's built-in software update process to load new books into the application. How did you come up with this idea?
For a variety of reasons. One thing that drove us toward this was gentle but insistent prodding from Apple throughout the dev process to stay away from selling books through our app. We'll be transitioning to server-hosted books later on though, once the collection has grown further.
Did Apple explicitly guide you away from selling books?
They guided us away from selling books directly through our app, which is against the terms for iPhone developers. We're hoping we can figure out an elegant workaround that they are fine with, but I want to stress that overall, they've been very supportive of this app, and have even been showing it off in the ongoing iPhone tech talks around the world.
How often will books be added?
I would expect to see several new books with each app update, the first of which should come later this month or so.
Will updates be free?
Yes. The app may become more expensive later on as it matures, but updates will remain free for all existing customers.
Since the books update along with the software, will users be able to keep/archive titles previously loaded into the application?
We have no plans to remove any books we release. Once the library size becomes prohibitive, we are planning to shift to server hosted books.
Apple requires applications to be under 10MB for download over cellular connections. Does this restriction limit the total number of books you can make available through Classics?
Not really, in that we are already pushing 20MB. We're hoping that we can eventually transition to server-hosted books while retaining the user experience though.
How many people were involved in the development of Classics?
Beyond Kaz and I, there were four designers who helped with various parts of the app (including the cover art, interface, and even processing illustrations for the books), as well as a friend and Web programmer who helped us create some in-house tools for correcting and formatting these books.
The Classics bookshelf interface has a unique look. How much effort went into this design?
Probably more than most people would think! The bookshelf interface for book management was inspired by Delicious Library's visual shelves (an app that Kaz worked on when he was 14). So starting from there, we worked with David Lanham on realizing our own flavor of bookshelf, and slowly refined the look over the next couple months, experimenting with various levels of decoration, tints, etc.
Of course, the other half of the bookshelf view are the custom book covers. As I mentioned before, Classics ended up being a passion project for all of us, and the designers really went overboard with the covers. (In a good way.) We started with the idea of procedurally generating each leatherbound book cover with different colors, sizes and such, with a unique "cover image" for each book designed to look like they were embossed on this set of leatherbound novels. Unfortunately, this ended up looking extremely bland. So after literally weeks of going back and forth on this with Dan Goffin, who was drawing concept art for book covers from the start, we settled on a much more colorful, and less restrictive style of fully illustrated covers.
I think this is the point where it gets a bit crazy. At this point, the concept books were looking much nicer, but we began to feel that the slightly simplified style made them look more like icons than real books. They looked a little fake. So the designers ended up illustrating these in high res, as if they were real books. The user for now actually never sees the vast majority of the detailing, but I think this level of detail adds a really unique level of polish to the app.
Will you port Classics to other systems, such as Android?
We haven't even investigated Android at all yet, but it's certainly a possibility. For now though, this remains an app we just personally really wanted on our iPhones!
Have you used/seen some of the other book-based iPhone applications? What's your impression of these?
Yes. And I feel like you are leading me on a bit with this question, but I'll take the bait and bite. I've tried a bunch of the other book apps out there, and frankly, the overall quality of these apps (in particular the "one-offs") horrified us, and only further motivated us to go full out with Classics. The only other book app out there worth picking up is Stanza.
How many copies of Classics have you sold? Have book publishers or others approached you about including their material in the app?
We've sold over 20,000 copies so far, though there hasn't been so much in terms of profit yet due to our initial investment in the app. We're optimistic though, and we're hoping some leads work out with publishers. There are publishers who want to work with us and sell books on the store, but the main issue for now is that there aren't many viable options for them besides selling one-off book apps, which is not ideal. If there's a nice way to do this though, we'll find it.
Ebook to iPod to Hard Copy Purchase
Peter Brantley
November 18, 2008
| Permalink
| Comments (3)
|
Listen
Hugh McGuire is loving Stanza, the free ereader app for the iPhone/iPod Touch. From the Book Oven Blog:
40,000 ebook dowloads-a-day. I've got 35 of them sitting on my iPod. If you are a publisher, think long and hard about that number.
The reason I have 35 books downloaded onto my Stanza is: a) it is easy, b) it is free.
What does this mean for your business model? I don't know, but I assure you that when I finish War & Peace, I'll be buying a hard copy. And I also assure you: I love reading on that little thing.
Q&A with Hadrien Gardeur, Co-Founder of Feedbooks
Mac Slocum
September 23, 2008
| Permalink
| Comments (1)
|
Listen
Feedbooks is a Web-based service that converts, catalogs and distributes ebooks in a variety of formats. Co-founder Hadrien Gardeur discusses Feedbook's system and future services in the following Q&A.
How would you define your company? Is Feedbooks a distributor? A digitizing service? A social network? Something else?
Probably all three. We already distribute a massive number of ebooks and most of our users currently use Feedbooks to discover and download public domain or Creative Commons licensed ebooks. But we're also working on various tools for authors and small publishers to create ebooks. We'd like to turn our readers into potential authors, and create a service where new authors can distribute their creations to a large user base.
Who is your typical user?
Do we really have a typical user? We probably used to have typical users when we mostly provided ebooks for dedicated reading devices: heavy readers. But that's not the case anymore, now that we've extended the service to the iPhone, too.
Why did you start Feedbooks?
We've seen a lot of very exciting services for music and video these last few years and I really believe that there's a huge potential for ebooks too, thanks to E Ink-based devices and multi-purposes platforms such as the iPhone and Android. I love reading and I'd like to create a great service where anyone can discover new books, and where authors can easily connect with readers.
Your Web site lists support for the Kindle, the Sony Reader, the iRex iLiad, the Cybook Gen3, the iPhone and other smartphones. How are you able to support all of these devices?
We use an abstract representation, somehow similar to DTBook, to store all of our books. We can generate a file on the fly based on this representation. Adding new formats is fairly easy thanks to this technology. We were the first service to distribute books in EPUB for this reason.
Which ebook format is most popular with your users? Which e-reader is most popular?
EPUB and the iPhone are probably the most popular right now thanks to our seamless integration into Stanza. The most popular dedicated device is the Kindle.
Have established book publishers used your service to create ebook editions?
No, we're still working on those features. I expect major publishers to use XML+XSLT or Adobe InDesign rather than a dedicated service. We're creating our publishing feature with the end-user or small publishers in mind rather than major publishers.
Do you plan to sell ebooks?
We do. I believe that free content and user-generated content in general shouldn't be in a different environment than the rest of ebooks. It makes a lot more sense to have both in the same environment and create an optimal experience for the user.
When will sales begin?
No specific date yet, we'd rather focus on building a good service first and then add this component.
Print on demand (POD) services seem like a logical extension for Feedbooks. Is this something you're planing?
Sure, I consider POD as another potential format for our platform. It's a lot easier to turn an ebook into a POD book than the other way around.
The Feedbooks RSS tool appears to be targeted at Kindle users who want to receive updated news and information from RSS feeds. Do you anticipate other uses for this tool, such as a blog-to-book service?
It's not targeted at Kindle users only. I use it every day on a Sony Reader, and it's actually quite popular with the iPhone, too. I've been experimenting with blog-to-book, there's a lot of such "blooks" (blog+book, serialized novels using blogs) out there. I created a catalog entry for Stanza to test how the readers react to these serialized novels. Such a tool could probably be very interesting for publishers, too.
Feedbooks and Lexcycle, the company behind the Stanza e-reader, have a close working relationship. How did this come together?
Lexcycle launched the iPhone version of Stanza a few days before we decided to release the first version of our new API. Marc [Prud'hommeaux, principal developer at Lexcycle] contacted me: they were looking for content that could be directly integrated into Stanza's online catalog. We exchanged a lot of e-mails with various information, and did a lot of work together to make sure that this would work from day one. There's still a lot of new features that I'd like to introduce and we'll continue improving both the API and Stanza in the future, to create an optimal experience.
How are publishers and others using the Feedbooks API?
I would describe our API as read-mostly for the moment. It's mostly useful for reading systems such as Stanza. Once we turn it into something that's read/write, the situation will be quite different and I can imagine various innovative publishing techniques based on this.
What publishing techniques do you foresee?
Publishing should be more of a seamless experience. We already use a lot of publishing tools (blogs, social networks etc...) and we shouldn't have such a gap between these tools and ebooks.
What are the biggest issues with digital conversion?
There's a lot of formats, and you can expect standards such as EPUB to evolve in the near future. But I believe that the biggest issue for publishers is to find the right balance between what users are allowed to do and the ability to preserve the layout and design of a book. The holy grail for publishers is probably something as powerful as PDF, but reflowable. Ebooks allow users to customize a lot of things and preserving the design of a book shouldn't be at the cost of this flexibility.
- Stay Connected
-
TOC RSS Feeds
News Posts
Commentary Posts
Combined Feed
New to RSS?
Subscribe to the TOC newsletter. 
Follow TOC on Twitter. 
Join the TOC Facebook group. 
Join the TOC LinkedIn group. 
Get the TOC Headline Widget.
- Search
-
