This post originally appeared on Joe Wikert’s Publishing 2020 Blog (“iBooks Author: Appreciating Apple’s Intent“). It’s republished with permission.
My question is simply this: Why all the fuss? Apple’s intent has never been to improve the book publishing industry. Just like Amazon and any other ebook vendor, Apple’s goal is to capture share of this rapidly growing segment. In Apple’s case, it simply decided to offer an authoring tool that’s capable of creating some pretty darned cool products. If Amazon were to do the same thing and create a terrific authoring tool for mobi or KF8 format, would the industry be as upset? I don’t think so.
How is this any different from the App Store model itself? Developers are creating apps for the App Store, and they know they’ll only run on an iOS device. They also realize they’ll have to go through Apple’s approval process before getting into the App Store.
Prior to the release of iBooks Author, the content creation and distribution model looked like this:
- Author writes material in favorite word processor.
- Author/publisher edit and convert that content into mobi format for distribution on Amazon, EPUB format for distribution through iBookstore and others, etc.
The exact same model still exists today, even with the introduction of iBooks Author. That’s right. Apple’s EULA doesn’t really lock you into its distribution channel for your content. That restriction only applies to a “book or other work you generate using [the iBooks Author] software.” All Apple’s really trying to do is prevent you from tweaking the output of its tool to create content for other distribution channels. OK, that’s kind of annoying, but far from the lock-in nightmare so many people are describing it as. Based on my interpretation, you’re able to use the same content as input to the iBooks Author tool as you’d use for a mobi-formatted product you want to sell on Amazon.
(I should also point out that I’m far from an Apple fanboy. Anyone who knows me realizes I dumped my iPhone last year for an Android-based Samsung Galaxy S II (and yes, I love it). I also tried to dump my iPad for a Kindle Fire but found the Fire user experience to be very disappointing. I’ll probably make the jump to another Android tablet later this year, once key apps like Zite are available. In the meantime though, I want to make it clear I’m not here to shill for Apple. If anything, I’m currently in a stage where I’d prefer to buy devices that aren’t made by the content providers. Samsung is high on my list, for example.)
Apple doesn’t have an objective to move the publishing industry forward. It sees an opportunity to reinvent this industry, and it feels it can do so within its own, closed ecosystem. It’s as simple as that, and it’s consistent with everything it has done in the App Store up to now.
Let’s also not forget that the iBooks Author tool is free. It’s not like we paid Apple $50, $100 or more for some authoring tool that we thought could work for all content formats and distribution channels. If the tool’s feature set is compelling enough, I’d like to think the other ebook vendors (e.g., Barnes & Noble, Amazon, Kobo, etc.) will have to come up with something at least as powerful for their own platforms. If not, they get left in the dust and Apple gains share. Seems pretty fair to me.
In the meantime, I plan to do some hands-on testing with iBooks Author. At first, I was discouraged because you can’t download iBooks Author unless you’re running Lion. I’m still on Snow Leopard, but an O’Reilly colleague sent me this link that shows you how to tweak a couple of settings so you can download and run iBooks Author on a Snow Leopard system. I just tried it, and it works fine. (You just have to carefully read and interpret the steps since it’s a translation from French to English.)