booktwo.org

So, I’m off to the SXSW Interactive festival in a couple of days, where I’ll be going to lots of talks, meeting people, and appearing on a panel. You should come to that if you’re around on Tuesday. It should be fun.

The panel’s about post-digital design, or what we could and should be thinking about when we can blend physical and digital formats in new and interesting ways. As part of my own preparations and thinking, I (surprise!) made a book.

The idea is, it’s a book to last you the week, through SXSW. A one-time pad for the festival. Customisable. Personal. Travel and accommodation details. You’re probably going to need those a lot:

Maps of Austin – different scales, and several basic grid plans. Useful for scribbling directions on, as well as navigation.

Planning diary. Schedule. All the talks that are happening, alongside your maps and diary. (Yup, that’s what the XML was for.)

I’ve never been to Austin or Texas before, so I stuck Wikipedia’s entry on Austin in there, and the Lonely Planet chapter on Texas (which you can buy and download here – nice). I did get in touch with Lonely Planet to discuss licensing this properly, but we ran out of time. One of the reasons this book is not for sale.

Finally, I wanted to use the book as my notebook for the conference – trying to avoid carrying around a guidebook, and a programme, and a schedule, and notes. (Remember the DIY Classic Notebooks?) There are 70-odd blank pages at the back, together with some helpful suggestions on what to write if you get bored or distracted.

That’s it. Pulled together in a few hours at the last minute despite planning it for ages. HTML -> XML -> InDesign for the talks schedule. Simple PDF resizing for the LP section. Basic-as layout for the rest, with some running heads and page numbers to minimise endless searching. Printed 10 through Lulu – £5 a pop, plus £25 to expedite shipping (because I left it until the last possible moment). Arrived in 4 working days. Done.

More photos at Flickr. More thoughts at SXSW and after. Do drop me a line if you’re going to be around.

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.

At the weekend, the fruits of several months of work at Apt finally hit the App Store in the form of Enhanced Editions‘ first title: The Death of Bunny Munro, by Nick Cave.

Enhanced Editions ebooks are a different breed to most, as our mission is to work closely with publishers to obtain the best material, and take advantage of every possible benefit of the ereading experience. This means taking every feature you’ve come to expect from good ereaders – including bookmarking, full-text search, adjustable fonts and type sizes, night mode, tilt scrolling (on the iPhone) and so on – and adding exclusive additional content, and the real coup: full text-to-audiobook synchronisation. The latter means you can switch between the text and the audio without losing your place, and we hope it’ll get people excited, and prove that ebooks really can go to new places, over and above the physical book.

For my part, I’ve written a number of posts over at the Enhanced Editions blog explaining some of the thinking behind the design and user experience, such as serif vs sans-serif and audiobook integration. Other members of the team have also written about designing icons for the iPhone and our attitude to DRM.

We’ve been working on Enhanced Editions for just over a year, and it’s been great to have been part of the team, and great to have produced an app we’re proud of. There’s more to come here – and we should really talk about ebook pricing and convergence at some point – but until Obama arrives, go check out Bunny Munro in the App Store now.

*

P.S. The trailer’s another fine job by our friends at Asylum Films, who made 25th Estate: This Is Where We Live.

In case you don’t read Times Emit (which you obviously should), Apt just released a fun little literary app onto the web that I designed and built: The Book Seer. I wrote about it over at TE (and had a bit of a rant about book data):

It’s very simple. It’s just pulling suggestions from Amazon and LibraryThing – at the moment. I’d like to pull stuff from more places, but it’s not easy.

…

Book data is hard, but it shouldn’t be. It’s also valuable, and that’s why Amazon ranks higher than most publishers for their own books, and why monopolies like the OCLC exist and why things like OpenLibrary are A Good Thing (and I need to have a proper play with their API). Data should be free. Representations of that data can then be used by all, and the most successfull will Rise. That’s the idea, anyway: things like this should be easier to build.

Peter’s also written a follow-up post, The Long Tailed Book Seer:

Seeing as the Bookseer is about books, and data, and openness, I thought I would share some of the early stats with those of you who are interested in such things. This is all based on the first few days’ traffic up to June 13th. (Whilst launched before then, we announced in on June 9th.) As well as being fun, I think that the data is a mild demonstration of The Long Tail in action.

Read the whole thing at TE, and of course, go check out The Book Seer…

I’m very pleased to announce that Doris Lessing’s The Golden Notebook, a collaboration between my employer Apt and The Institute for the Future of the Book, is now live.

Several months ago we heard that the Institute was setting up in the UK, and we approached Chris Meade with a view to working with if:book London on a joint project. The result of this was the realisation of a long-cherished idea from Bob Stein, the founder of the Institute. Bob had recently reread Doris Lessing’s classic novel The Golden Notebook, and wanted to bring it to a new audience by creating a public reading group, composed of younger readers.

With Lessing the recent recipient of the Nobel Prize in Literature, it seemed an appropriate time. We approached HarperCollins, Lessing’s publisher, and persuaded them to allow us to use the full text of the novel online, in the most accessible format we could. We built a website which allows the text to be read, bookmarked and commented on, page by page; a blog for the readers; and a forum where the public could discuss the novel, and the reading of it – all built on free, open-source software.

This Monday, November 10th, the reading begins. Seven readers, invited by the institute and including novelists, screenwriters, critics, and journalists, will read and comment on the book, and everyone is invited to join in. We’re very proud to be a part of this collaboration, and hope it’s a great success.

I’m pleased to tell you that bkkeepr, my project to create a Last.fm-alike for reading (and more besides) now has an API.

An Application Programming Interface (API) is essentially a machine-readable version of an application, and more specifically, the data in contains. bkkeepr is first and foremost an application that does stuff with data, and bkkeepr.com is the human-readable version of that application. What an API does is allow third parties to build small applications, widgets and so on that utilise that data in new and different ways. (This is another post, but I pretty much believe that everything should have an API. And not just everything on the web. E.G.)

bkkeepr is itself built on Twitter’s API, and uses data from a wide variety of other web services, including LibraryThing, Google, Amazon and others, via their APIs. So opening up bkkeepr’s data in turn is something I’ve intended to do from the beginning.

The bkkeepr API is very basic at the moment, allowing you to do two things: get all of a particular reader’s reading data, and get all the reading data about a particular book. There’s more information about it here.

The most important function of the API, to my mind, is that it gives users control over their own data. It’s not locked up in a database over which they have no control, and they can pull it out and store it elsewhere any time they like. I’ll say that again: it’s their data, not mine, and they should have control.

It also gives people the opportunity to build cool things. Here are some examples, some dull, some fun, that I’ve been thinking about:

• bkkeepr ‘bestsellers’ – hot books, favourite books, the most read. Charts, and suchlike.
• Find a friend – who’s reading similar things? I like this particularly as it would allow you to branch back to Twitter – or any other service – and find new people with similar interests there.
• Better widgets (because frankly, the current bkkeepr badge is pretty basic).
• Reading speed – silly, because I don’t think the speed at which you read means anything, as long as you read at all, but, like Dopplr’s personal velocity, it’s a neat data toy, and could be implemented fairly easily with book page numbers from Amazon’s Associates API.
• Pretty stuff with covers and calendars (in the spirit of the awesome LastGraph).
• I’d love to see booksites implement a ‘who’s reading this now?’ widget, but realistically I think bkkeepr needs a few more users to see that happen…

There are a tonne of possibilities, and I’d love to see people do interesting stuff. bkkeepr currently has just over 500 users – not many, but I’m hoping adding features like the API and its results will draw more in. To those who say that an API is just a way to outsource the development of an application to those with more time on their hands, I say: yes. Yes, it is. Have fun.

HarperCollins have just launched their online slushpile site, authonomy.com, in private beta. Authonomy allows budding authors to upload chapters of their work for the rest of the community to read and comment on.

There’s been a lot of speculation about how this would be implemented, and at first sight it looks pretty good – HC haven’t overreached themselves, they’ve simply created a site for people to join, upload their work, and read that of others’. Sounds simple, but many similar projects have failed thanks to scope creep.

Every user gets a profile where they can create a virtual bookshelf showing which other writers’ works they’re supporting – authors get the chance to create their own “cover” for a work too, a pointless but satisfying little feature which is sure to go down very well indeed.

The real challenge, of course, is to persuade wannabe writers to post their work at all – in my own personal experience, unpublished writers are terrified of their work being ’stolen’, enough to be suspicious of publishers themselves, let alone your average web surfer. The Front List, a previous attempt at a “YouTube for books”/”crowdsourcing the slushfile”-type site, solved this by hiding everything from non-members; one approach certainly, but not one likely to bring in the crowds.

Authonomy’s FAQs wisely address many of these concerns, and they haven’t done too much to break the site in the implementation, short of disabling right-clicking on book text. As they put it, “if someone really wants to pass off your efforts as their own they’ll probably find a way” (Hint: turn off javascript). Their real attitude to the problem is more sensible: “here at authonomy, we believe that your talent is better displayed than kept hidden – and that the chances of good things happening are more likely the more hands your manuscript passes through, and the more people you enlist in your support.”

On the technical side, users upload books by chapter (as few or as many as they like) in Word or RTF formats, which are then displayed as is – imagine hitting ‘Output as web page’ in Word, if you’ve ever done such a thing. It doesn’t result in the prettiest pages, but it does mean the book appears on the site as the author made it, which is, quietly, quite a thing.

Authonomy has been a long time in the making, and in the wake of the disastrous relaunch of HarperCollins.co.uk, we feared the worst. But Authonomy (still very much in Beta, which HC.co.uk can’t claim to be) looks like a very good little set-up which is bound to get plenty of attention and users. Nice one, HC.

Things Magazine just pointed to the growing cult of book covers online – Flickr groups for good looking books, old paperbacks, graphics and more, and similar projects like their own, wonderful Pelican Project. There are also plenty of blogs dedicated to the subject, and Penguin have spent the last couple of year deliberately turning them into a fetish item.

But why? Only today we learn that books are the number one internet product, and the weighting of book covers on ecommerce sites has long mystified me. We’re still selling books by the cover, even though their original purpose was only ever to attract the eye in the physical bookshop; online, they become pixelated blurs, lacking any of the distinctions of colour and typography that obsess designers. The covers are no longer representative.

Even actual ebooks are still represented by “covers”. It’s not unique – this continued reliance on a visual signifier for a virtual product is paralleled in Apple’s iTunes store and, particularly, Coverflow, and you see it too in the ‘boxing’ of downloadable software.

We say, “don’t judge a book by its cover”, but we always do. The web, and particularly the rise of the ebook, should allow us to make better, more informed judgements about what we buy and read – or at least, that judgement should be based on the skill of the writer, and not the illustrator. You don’t buy shoes for the box, do you?

Is there a better way of communicating content?

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?

Matt Webb, of Schulze and Webb, gives this explanation, which pretty much nails it:

A book is designed and manufactured… We discover a book, somehow. We wish for it. We select it, maybe out of a possible half dozen alternatives. We purchase it, then show it off. We discuss it, reviewing it if it’s great or if it’s terrible. We might sell it on.

A bookstore on the street, a traditional bookstore, now seems quite inadequate. Or at least, inadequate before they started doing evening book talks, supporting book clubs and having employee recommendations. But inadequate—it’s really only optimised for purchase.

Amazon’s success could be seen less about the convenience of being online, and more about the fact it is present in more of your moments of engagement with a book.

Amazon understand that we live alongside books. We cross paths with them at all of these points. If Amazon can be present in more of those, we like Amazon more, we encounter them more, and they do better.

Anyone want to argue with that? There’s a lot of work that needs to be done in making sure Amazon doesn’t become the next Tesco/Wal-Mart and control every aspect of our lives (The Book Depository’s redesign is a small step in the right direction), but if you want to understand why traditional bookshops are failing, why in response publishers are being squeezed until the juice runs clear, and why Amazon seems to have so effortlessly inserted itself into the world; well, there you go.

This quote comes from a talk on Interaction Design. You can read the whole thing here. It’ll explain the picture at the top, too (which is Matt’s).

Why am I reading blogs and wikis and transcripts about Interaction Design and Planning and hacking (the good kind) so much lately? Well, it’s because I’m no longer involved in the acquisition, manufacture and distribution of books – publishing’s industrial age – and I’m trying to understand how we create, connect to and communicate literature – particularly, without just creating more ads. Book 2.0 is now my day job.

Once again, I point back towards booktwo’s opening statement, which I always re-read when I’m not sure what I’m doing. The need to think clearly and openly about these issues, and break from the past. Lagerfeld’s dictum: “Throw everything away!” I’m not quite going to do that, but I admire the sentiment.

“If some Javanese sorcerer or Native American shaman possesses some precious fragment I need for my own “medicine pouch,” should I sneer & quote Bakunin’s line about stringing up priests with bankers’ guts? or should I remember that anarchy knows no dogma, that Chaos cannot be mapped–& help myself to anything not nailed down?” – Hakim Bey