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.

Inspired by the Japanese iPhone/Book mashup that appeared in the Stop Press links recently, I made this rough concept of an in-book mobile app, riffing on ideas of the “enhanced edition“.

Imagine if when you got a book, you also got a mobile app that contained the footnotes and index, supporting material and the searchable text. The app sits inside the book itself. Search the app for “Leonardo da Vinci” and it points you to the relevant pages in the book. Supplementary material is accessed by typing in the page you’re on in the book. It includes biographical information, galleries of high-resolution, zoomable images. Take notes, save and email them. Find other readers nearby. Annotate the text, and keep those annotations in the right place – connected to the book itself, but accessible anywhere. For series books the possibilities are even bigger: linking a collection via a digital index and archive. And its updatable: the author can add in material to the book indefinitely after publication – and pitch their next one when it comes out.

It’s a thought, isn’t it?

After initial doubts – why would Amazon deliberately waste all that investment in the Kindle hardware? – I did come to the conclusion that the Kindle and iPhone demographics, while they certainly overlap, are by no means mutually inclusive. I don’t have figures on this, but my presumption is that the iPhone’s younger and/or early-adopter audience is not quite the same as the Kindle’s slightly older, less techy, but more hardcore booky audience (heavy genre readers, in romance and sci-fi, reading up to several books a week, are the core Kindle audience, I’ve heard). The Kindle’s larger screen and seamless connection to Amazon speak to a different audience than the iPhone’s portability and rootlessness.

Thoughts?

• 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?

And you know what? It was great. It was easy to read. It didn’t strain my eyes. It slipped into my pocket when I changed tube trains and it jumped straight back to the right place when I slid it open again. Alex has a few good points on problems with booksinmyphone’s interface, but overall the experience was a joy. I was done in a couple of days – slightly above average for me.

I recently had a go at reading Charles Stross’ Accelerando in the ebook version – a similarly great, near-future novel – and gave up about half way and tracked down a paper copy. And in hindsight, the reason was obvious: I was reading it off a laptop. That’s miserable. Put it on a phone, and it immediately becomes wieldable.

My phone is a Nokia N95. It fits in the hand, but has a nice big screen (pictured right, courtesy, again, of Alex) – about 40mm x 55mm. Comparing that to the 100mm x 160mm block of text you get on the average B-Format paperback page means you get about a third of the line length, and a third of the page height. But once again – it really didn’t seem to affect my reading. I even found myself reading it in bed, even when I’d only started out of necessity when I found myself on a bus without a book.

Does that imply it was better? Well, I’m not going to go that far – yet. My paper books don’t run out of batteries, for starters, and the platform is still suffering from format fatigue (Mobipocket has the best range, but they’re still priced too high, and the free stuff doesn’t cut it), but I’ll definitely be reading more this way. And with the recent news that cellphone novels – books not only read but written on mobiles – are beating out the bestsellers in Japan, I’m not the only one.

So, it’s finally here, and damn, it’s still ugly. Really, really ugly. Go watch the video demos (short one at the top, longer one lower down). But it has some things going for it.

There are a lot of touches I really like, like easy ordering of low-price ebooks direct from Amazon without having to be near a computer. Online back-up of your books is very smart – one customer losing their whole library after dropping one of these in the bath would pretty much kill it. The big page-turner paddles on the side will be good for peoples’ frequently contorted, curled-up-on-the-sofa reading positions, and the dog-ear bookmark is nice and friendly, although the purists will probably hate it.

But there’s a lot not to like, even beyond the let’s-party-like-it’s-1989 styling. E-ink just still isn’t good enough: there’s the ‘black flash’ as you turn the page, and the snail-like refresh speed means they’ve had to put in that scroll-wheel barometer thing in the side, which is not good. The whole feeds thing is a misnomer: you have to pick ‘your feeds’ from an Amazon-approved list (currently numbering 308), which is great if you just want Boing Boing and the NYT, but pretty rubbish if your tastes are more eclectic – and you don’t want to pay 99 cents for the privilege (is that a one-off or a subscription?). And the killer for me is that you can only read your own documents by emailing them to Amazon, who’ll convert them and add them to the Kindle ‘for a small fee’. Whoa. That’s just stupid. It’s also such a waste of the rather clever connectivity hardware they’ve packed in there.

Still, Amazon aren’t making this for me – they’re making it for regular, heavy readers, who are book- and not computer-focussed, which is an excellent decision – they will certainly please more people – and explains the video endorsements from Toni Morrison, James Patterson and others. It’s not for techies. We’ll see if the $400 price tag is attractive to non-techies.

It is, without doubt, the best ebook reader out there because it has the iTunes-like connection to all the books you can get, built in. That’s the USP. But I still don’t think we’re going to see mass ebook take-up any time soon, not until e-ink improves and we sort out a format that can move seamlessly between different devices, like mp3. If I can read it on this, I should be able to read it on my laptop, phone and even TV too.

And could someone please explain why they used ‘profligate’ (adj. utterly and shamelessly immoral or dissipated; thoroughly dissolute, recklessly prodigal or extravagant.) as their example word from the dictionary? Reminds me of this story.

UPDATE: For more on the Kindle, you could do worse than Buzzfeed’s roundup.

Some people are going to hate me for this, but I think it’s great: The 250GB Book.

I did agonise over cutting up the book. I did reject several others in the charity shop because they were too nice to do it too, even if they were just going to rot on the shelf anyway. I did cut myself several times. Still.

I also recently ordered one of these, and I’m waiting for it to arrive. Any suggestions as to what I should do with it when it does?

Despite my repeated entreaties, no one bought me a ticket for O’Reilly’s Tools of Change conference, on this week. It looks like a lot of interesting people, talking about important stuff.

Pleased to see that Manolis Kelaidis’ bluebook project, which I wrote about last year, has made an impactful appearance, and I suspect there’s a lot of similarly cool stuff being discussed.

Places to find out more: there’s the Conference blog, Andrea Laue’s jusTaText seems to be on the ball, as does Jeff Gomez’s Print is Dead, and there’s always Jeremy’s excited Twitter. If you know others, do let me know.

In the meantime, I’ll be over at London Lit Plus…

As digital media in the form of portable devices, touch-screens and pervasive wireless networks offer new possibilities for interaction, the traditional book starts to look rather featureless when compared to electronic versions. But the traditional book has many advantages too – not least the comfort of tradition itself. The blueBook aims to find a compromise between these two objects, between the digital and the physical.

The blueBook created at the RCA and pictured here is a traditional book over-printed with conductive ink. This conductive ink creates hyperlinks on the page which, when touched by the reader, activates a processor concealed in the cover of the book. This processor then connects via bluetooth to a nearby computer, triggering different actions.

For example, a children’s book on animals might activate sounds and videos on a screen when the printed picture of the animal is touched. Reference books may contain inline glossaries linked to Wikipedia or Google. Keywords in novels trigger incidental music. Buttons on academic papers connect to discussion forums or send feedback to the author.

Admittedly, most of these tasks are or can be done entirely in software by true ebooks, negating the (currently) high costs of printing in conductive ink and binding circuitry and processors into a physical book. But the blueBook does provide a bridge – for children, for the elderly, for those less comfortable with new technology – to ease the transition from the printed to the digitised book. Such devices are going to be much in demand, and the cost of their production is dropping rapidly.

Manolis has now graduated and is looking into ways to develop and commercialise the book, and tells me he has been talking to major publishers who seem very interested in the idea. He is also working on a tentative business plan for a company that would develop and design such books. However, it looks like that mass-production could take some time so the next stage is likely to be a short-run, specific-application implementation of the technology. We look forward to seeing where this goes.

Nicholas Evans was the blueBook’s graphic designer and it was produced by Book Works. You can see more images in the booktwo Flickr stream. Manolis Kelaidis can be contacted at manokel at gmail.com.