Screen shot of Apple iPad in use
Image by Tom Raftery via Flickr

The introduction of the iPad marks the beginning of the end of price controls for ebooks, but not because, as some have speculated, Apple’s more flexible pricing controls in the iBooks store provide leverage against Amazon. Of course, Apple’s more flexible pricing controls do provide leverage against Amazon. As David Crotty observed in a recent Scholarly Kitchen post, Macmillan wasted no time in applying that leverage. But Macmillian’s skirmish with Amazon strikes me as a battle waged after the war has already been decided (which perhaps explains why Jeff Bezos was absent from the battlefield as John Scalzi has noted in a blistering critique of Amaon’s handling of the situation).

The real reason the iPad marks the end of pricing controls for ebooks has nothing to do with Apple’s iBooks pricing policy. In fact, the iPad renders Apple’s own ebook pricing policy as irrelevant as Amazon’s. The real reason the iPad renders any ebook pricing policy irrelevant is because the iPad is not a dedicated ebook reader.

Why does this matter? It matters because unlike the Kindle (and unlike the iPod when it comes to music), there are multiple paths publishers can take to deliver content to the device.

It is important to disambiguate iBooks from iPad. iBooks is Apple’s as-yet-to-be-launched online store for ebooks. Presumably iBooks will occupy another tab in the increasingly misnamed iTunes Store. Already there are tabs for the App Store, Audiobooks, and iTunes U along side Music, Movies, TV Shows, and Podcasts. Just as the App Store has long had its own app on the iPhone, iBooks will have its own app on the iPad (and iPhone/iPod Touch). Essentially this app will access just the iBooks tab in the iTunes Store.

In introducing iBooks, Apple is using a move from its own playbook. When the iPod launched and Apple first introduced the (then appropriately named) iTunes Store, Apple set price controls on the music it sold. There were a lot of reasons for this. Apple was competing against “free,” which was the price most people were paying for music obtained online at that point in time. A simple pricing model was the way to go.

Apple also was (and is) in the device business. The easier and cheaper they make it buy music, the more people will buy iPods. The more people who buy iPods, the more music they will collectively buy. And so on (the “Infinite Loop” strategy if you will).

Perhaps most importantly, Apple had (and arguably still has) a de facto monopoly on the legal online distribution of music and so could get away with it.

But music and books are not the same thing, and Apple is not in the same position with regard to ebooks.

Apple is not competing against “free” in the same sense it was (and indeed still is) when it launched iTunes. While libraries do, of course, circulate free books, Apple is competing for the people who prefer to own books or who prefer to read electronic books (which, in many cases, are not available to library patrons). Such readers are used to paying variable prices for books. Apple does not need to do anything except allow book-buying customers to replicate their current behavior.

But there is a far more important distinction between Apple’s foray into books versus music. When the iPod launched, there was only one way to get music on the device—iTunes. You could buy music via iTunes or rip CDs into iTunes. In either event, you needed iTunes (and you still do—Apple has effectively very little competition to this day).

Unlike music publishers, book publishers have not one but at least five ways to deliver content to the iPad:

  1. The iBooks Store – Publishers can submit ebooks in EPUB format to the iBook store. In this case, publishers would need to agree to Apple’s rules regarding pricing (at least for now).
  2. Build an app – There are many books that already have their own apps. While developing a bespoke app for each book would be cost prohibitive, there is nothing to prevent a publisher from developing a standard app into which they flow a large number their titles (like a template or a set of templates). Penguin could, for example, build an app for their entire line of literature classics. The app itself would be free but then users could purchase individual titles within the app. There would be no price restrictions on such purchases.
  3. Use a third-party app – There is nothing to prevent Barnes & Noble, Safari Books, Baker & Taylor, Ingram, Smashwords, Scribd, and others from developing their own apps to deliver ebook content to the iPad. Amazon already has one for the iPhone which will presumably deliver ebooks to the iPad on Day One. Again, there are no price restrictions on such purchases (except for those imposed by the third party).
  4. Use your Web site – Most ebooks are currently read online via PCs. As Steve Jobs emphasized repeatedly in his recent keynote, the iPad is designed to be a great Web interface. Publishers can put their books online, behind an access wall if they’d like, and readers can access them online via the iPad. Alternatively, publishers can simply sell the PDF files they already have via their Web sites, which I imagine will look very nice on the iPad. Not only are there no price restrictions using this method, but there is no revenue share.
  5. Third-party Web sites – These might include Google Editions, Scribd, or any other online ebook seller that sells or displays ebooks for the Web.

Of these five paths to the iPad, only the iBooks Store has any (Apple-imposed) price restrictions. But Apple will be forced to remove even the iBooks price restrictions in the very near future.

Apple will face increasing pressure from publishers using the other four channels outside of iBooks to deliver content to the iPad. Scholarly and professional publishers, who have long been utilizing the Web for ebook delivery, may very well lead the way on this front.

A little pressure will be enough because the price point for ebooks is really not important to Apple for the simple reason that iBooks is not the center of gravity for this device. The only reason anyone bought an iPod (until the launch of the iPod Touch anyway) was to listen to music. The only reason anyone bought a Kindle was to read ebooks. It was important to establish just the right (from the device-maker’s perspective) price point for content on these devices. Reading ebooks is not the only—or even primary—reason most people will buy an iPad. At the moment, Apple wants to woo Kindle users and so needs to ensure that ebooks are not substantively more expensive in iBooks than via Amazon. But in a few months, as ebooks make their way onto the iPad via other routes, as native applications are built for the iPad, and as Amazon grudgingly retracts their pricing policies in order to ensure they receive top tier ebooks upon release, Apple’s pricing policy, flexible as it is, will evaporate.

magical ipadThe other factor to bear in mind is that, while Apple may be first to market with a “magical” tablet (computer makers, including Apple, seem to dip their toes in the water every few years with a tablet of some kind, but they have all previously neglected to include magic, thus ensuring their failure—duh!), they will not have the market to themselves for long. Amazon has already purchased a company that makes touch screens and is rumored to be working on a “SuperKindle.” Sony is hardly one to shirk from a fight. Microsoft has been not-so-secretly developing a new two-screen tablet for some time. Google is now in the device business and has its own mobile OS. Then there is Dell, HP, Leveno, Barnes & Noble—the list goes on.

With all these tablets—all with multiple routes of content delivery for publishers—device makers will not be able to maintain price controls. There will be too much competition and too many routes to content delivery.

Victory: Publishers.

Before we break out the champagne and celebrate, there is one small wrinkle to consider, which I explore tomorrow in a follow-up post:

Why the iPad Marks the End of Price Controls for eBooks—and Why Publishers Have Lost

Reblog this post [with Zemanta]