booktwo.org

Tomorrow is T-day. Or iDay. Or whatever. It’ll be fun. Nobody knows *anything* yet. Well, apart from the folks at McGraw-Hill and Hachette, probably Kobo, and a whole host of others. But for the purposes of this discussion: nobody *knows* *anything*.

About the Tablet, that is. Because, actually, we know quite a lot. We know about authors and writing, and editing and publishing, and bookselling and reading. We know and understand the long-form narrative and its place between people, and in society. And I’m more comfortable with Apple getting in on the act than I am about Amazon, because Apple aren’t in the content game, and Amazon definitely are. And if Apple swoop in and solve ebook distribution like they solved (legal, paid-for, mainstream) music distribution with iTunes, then great. Amazon are having a pretty good crack at that with Kindle too, but I’d like to see more involvement from someone without such an aggressive history of pressuring publishers until their bones show (although I’m under no illusions), and Apple have a history of producing devices and interfaces that make people go “Oh, OK. I get it now. Neat.” Amazon are also showing signs of a more open, mulitplatform approach (iPhone app, epub, etc) but that’s another conversation.

Publishers have been confused about their roles for some time. And I’m trying very hard not to be inconsistent on this, because I’ve spent several years urging publishers to get on board with new technologies and try new things, but equally I hope there’s space for a lot of publishers to get back to concentrating on what they do best: acquiring, editing, producing and publishing books. I’d like to have seen more happen in the last few years, but if it hasn’t, we should probably stop scrambling to get on the latest bandwagon (vanilla Books-as-Apps, I’m looking at you), and concentrate on the basics: ebook production, metadata, integrated marketing, quality and consideration. There is a lot to be done, but this or that device will never be the be-all-and-end-all of the future of publishing.

O’Reilly’s Tools of Change for Publishing blog has a nice series of posts on books as ebooks as applications:

• Linking Books with the Web-Way of Thinking
• Treating Ebooks Like Software
• A Big Boost to Books as Apps?

I just want to voice something that has been bothering me a little about this (and given some current projects, may come back to bite me):

Books are not applications, or software. They are words.

I think there’s a danger inherent in regarding books as something to be run rather than something to be read. This argument is a bit hazy because a lot of book apps (such as booksinmyphone’s Java apps) are really just wrappers for the text.

But by creating multiple versions of books – rather than agreeing on a single format (e.g. but not necessarily, ePub) and building separate software to display that – we’re heading down a road of locked-down, device-specific book technology that is antithetical to the nature of the medium, and costly to publishers. If only those publishers that can afford to spend the time (not necessarily money, the time alone has a cost) creating huge ranges of different applications can get their books onto the marketplace, it won’t be the rosy future for niche literature that some versions of the ebook story predict.

The sheer replication involved – reproducing the same lines of code over and over again for each book in a library – bothers even my low sense of efficiency and programmatic elegance too.

Of course, this development is not of the choosing of anyone in books. It’s a short-termist, technological hack, to get books onto closed platforms like the iPhone and other smart phones, and in large part it’s caused by the development of the App Store, which provides us with a sneaky way of getting book texts onto phones while there’s no equivalent of the iTunes Store for text files. But I’d much rather see a Book Store selling files to be read by standalone ereader apps than this glut of mini-apps.

Such a path would not prevent publishers building their own, branded and self-promoting, ereader apps, as I’ve previously suggested, but it would massively widen the interoperability of ebooks and ereaders, which readers will only thank us for. Perhaps we should be looking at some other hacks instead?

So the iPhone 2.0 is here, and with it a slew of reading apps. There are two approaches here: create a standalone ereader that can be used to read ebook files, or create standalone apps for each book.

The former is definitely better, and the reader of choice so far appears to be Lexcycle’s Stanza, an open epub reader that’s loosely tied to FeedBooks, enabling you to pull down a bunch of free ebooks directly, or search for a whole lot more. Getting ebooks (or any other files) onto your iPhone/iPod Touch is not easy however, which is where the standalone books come in.

AppEngines currently have a whole bunch of these in the App Store – the usual assortment of out-of-print classics and weirdness. They’ve swamped the Entertainment category, in fact, to the extent that they’ve posted an apology on their site: “We share your concerns that our ebook applications are taking up too much space in the App Store. … We will not submit any more books until the situation is resolved.”

No such apology from ZappTek however, whose Legends series of books are also highly visible in the App Store Entertainment category. But wait, closer inspection shows that all these books are by one author: Michael Stackpole.

So what’s happened here is that a single author (or friend of) has got a stranglehold on new, accessible literature on the iPhone. The iPhone is currently the most sought-after piece of tech on the planet. It stands a very good chance of leapfrogging the frankly rubbish Kindles, Iliads and Sony Readers of this world to become the default ereader of choice. And one man has seen that, and done something about it. It’s the literary equivalent of shouting FIRST! in the comments. I think he kind of knows it too.

Anyway, for chutzpah, genius, foresight: booktwo salutes him.

… and wonders why if it only takes one guy to craft a pretty good ebook delivery system *in time for the App Store’s launch* and get it out there, how long before some publisher fulfills their responsibility to the authors and readers, and does something similar? We want to read people, and while I have a lot of respect for Mr Catchpole, Serpent on The Station isn’t really my thing, but, as Peter’s noted, what else is there?