Quote:
Originally Posted by Jellby
If I may. I see the point in creating an ePub3 over an app if one is interested in having some kind of "archival" quality. Even if no reader is capable of showing all the features as intended today, at least the specs are there and the code and markup will be available to be displayed in a future reader or converted (even if manually) to a future format. An app is disposable. Even if you keep/publish the source code, it will need a programmer to understand/convert it, an ePub3 can be more portable, but less usable in practice.
|
Jellby, mon sweetie patootie:
Sure, but we all know that ePUB specs change, too. We can sit here and say, "oh, the IDPF is moribund and the Committee is DOA, but the reality is, ePUB specs change. And of couse, Apple--the clearly designated hitter for this--changes their own s**t all the time. The likelihood that the app would be valid longer than the eBooks...meh, I give it a 50/50%,
especially given that we're talking multi-media and Apple.
The biggie really is cost. An app will set you back $1200 and up, and you need one for iOS and one for Droid. So, 2x the price. An eBook will typically be
much cheaper, but it does
far less.
Given how
abysmally eBooks sell on iBooks-cum-Books on iOS, honestly, I wouldn't invest a lotta dough in it, (compared to Kindle), but...that's the publisher's dominion and choice.
Hitch