There’s a great deal of buzz on the Internet about Apple’s iBooks Author App. Most authors and publishers haven’t used it or refuse to use it, usually citing Apple’s EULA agreement. Controversial as it may be, the announcement of the Author app was exactly what I’ve been waiting for. You see, I’m obsessed with ebooks. More than that, I’m madly in love with enhanced (interactive) ebooks. What follows is a fiction author’s take on the EULA Agreement as well as a rundown of my experience using the app to re-release my first novel this past week. Curious about the app? Read on.
The usual way to code ebooks. *sigh*
When Spirehouse Books released my novel, Artemis Rising, last September 2011, I went all out designing that thing with specialty coding. I spent about four months learning how to design, format, and code different versions for iPad, Nook, and Kindle. The process was clunky, glitchy, and slow. I loved every minute of it (remember, I’m obsessed?), but I found myself yearning for a better way.
Until now, there wasn’t a better way. Authors often mention Smashwords as their go-to aggregator for publication. But Smashwords’ coding and design is plain and lacks the capability for enhancements. Because ebook readers are essentially still in their infancy, they are riddled issues that require non-standard coding, workarounds, or simply giving up on desired design elements because valid code won’t work.
[flagallery gid=1 name=Gallery]
Enter the iBooks Author App.
I snapped up an iPad and I already had a MacBook. I just spent a couple of days learning the Author app and created an iBooks 2 version of my novel, which I successfully uploaded. I’ll get to the details in a moment, but my initial reaction? FREAKIN’ AWESOME.
Here’s a rundown of the elements I used most often in the process:
It took me four months of research, testing, and failure to realize I couldn’t manually code in my book trailer (still have no idea why it wouldn’t work). How did I do it with the Author app? I dragged the .m4v file from my desktop into the Intro Media section of the app. Done. (And no coding.)
Took me a couple of weeks to learn how to center a damn photograph for iBooks. I kid you not. But once I learned how, it was easy! *double sigh* One of those fun glitches in the iPad coding, you know. Anyhoo, as you can imagine, dragging and dropping photos into the app is effortless. What’s really cool is that as you move photos around the page, smart rulers and arrows help you line them up to other elements. Can’t tell you how helpful this was, as I had special glyph GIFs and another large image of a map on all 28 of my chapter header pages. Whoa. Resizing is a cinch, but the app is not set up to allow you to edit the photos themselves much. I suspect they’ll expand that capability in a later update.
iBooks fonts kick everybody’s butt. Seriously. iBooks simply has more font selection and more typographical features to add to your design. No other device even comes close in this regard. Took me a bit to test the app’s limits on font manipulation, but in the end I just went with what pleased my eye. I really wanted to delete the chapter header text and insert my own graphical title for chapter headers, but alas, I couldn’t get it to work. I’ll keep testing, because I could handcode it (took me several weeks to figure out that specialty coding too) in the previous version of my iPad epub file. I’ve not even attempted to try any custom html coding in the Author app. To be honest, I didn’t want to bother with coding since most of what I needed was already available in the app.
I’ve not played with every method or tried to import text from multiple sources. I simply copied the original text from my Word file (which was properly formatted with clean styles, etc.) and dumped the whole manuscript into the app. I hear from other sources on the Internet that there are easier ways. But I was playing around with how I wanted to format chapter header pages, so I wanted to try this method and take it slow. I then added in a chapter header page after deciding that that was preferable to using the “Preface” page for a novel. Which brings me to….
Chapter header pages
Everyone knows chapter pages are where most of your design elements shine. And Apple does an amazing job here, designing some beautiful elements that take advantage of the horizontal and vertical views of the iPad. A note on the views though: in general most elements on the chapter pages must be designed twice: once for the vertical view and once for the horizontal view. And just because your design looks purdy in one view…Well, much of my previewing and editing work involved double checking both views to ensure that the reading experience was optimal all around. I spent a lot of time playing with the first chapter header page, because I knew that once I had that perfect, I could then duplicate that page for all my chapters to save work time. That was fantastic. After the chapter header pages were set, I simply added one page to each chapter and dumped my chapter text into it. Pages were added by the app to fit the text. Voila!
Artemis Rising has a glossary of Portuguese and Latin words in the back matter. In the old method, I used InDesign to hyperlink every word and then exported the book as an epub file (a very time-consuming process). The glossary feature in the Author app is to-die-for easy to use. I highlighted each word and added it to the glossary with the click of one button. Later I went to the glossary section and pasted in each definition. That’s it. When the reader clicks on one of those special words, a little bubble pops up and gives them the definition right there. They don’t even have to navigate away from the page. Woot!
Previewing my design progress was ridiculously easy. I have iBooks open on my iPad. I plug the device into my MacBook. I hit the Preview button in the Author app. I wait a bit. Presto! The new version pops in and I get to check out my updates.
TIP: Be sure to download the iBooks 2 app on your iPad before attempting to Preview for the first time. Without it, you might run into issues. I did.
Elements I want to try next
I didn’t get a chance to use every feature in this first go-around. But I have big plans. I want to build a photo gallery of my book trailer production photos (all taken by the brilliant Beth Furumasu) as bonus back matter. I want to create an interactive map of my setting (I already have a map created in flash, but the folks at Apple are in a whiny fight with Adobe over Flash, so I can’t use it. Meh.) But I might be able to insert my own HTML5-coded map or use the interactive widget within the app itself. Still exploring that. Doubt I can find a use for the 3D widget for my novels, but one never knows. =)
Should you use the Author app to design the iPad version of your book?
Would I recommend iBooks 2 and the iBooks Author App to indie authors and/or small publishers? A resounding YES, given a couple of caveats:
- You’ve obviously got to have the hardware (an iPad and some type of Mac) and software (Lion OS X) needed. The app itself is free.
- You’ve read the EULA and feel comfortable with what you are getting into.
- You are interested in doing an enhanced ebook–it’s great for fiction or nonfiction.
My initial thoughts on the EULA Agreement controversy
The agreement itself is short-sighted and ambiguous. That goes without saying. But naysayers are forgetting one small detail that makes the current EULA’s strictures irrelevant for now: the ebook files that the iBooks Author app creates are far too complex for any other current e-reader device to display properly. In other words, you can’t read my Author-created novel on any other device than iPad, because devices like the Nook and Kindle aren’t sophisticated enough…yet.
I consider the Author app a beta. A test. A glimpse of the future. If Amazon is smart (please be smart!), they’ll hire a programmer to create a similar program and make it open to both PC and Mac users. And Barnes and Noble? They’d best get on it, too, or they’ll be the first of the Big Three to kick the bucket. I’m not even counting poor, dead Borders.
Apple’s most foolish move is to lock up their powerful programs and apps from PC users. (Anybody else think it’s ASININE that we can’t read books we’ve bought through Apple on the Web? Silly. iCloud, where’s my damn book? *narrows eyes*) But in this case, that hoarding and elitest tendency is, as I said, irrelevant. They are well aware that no other device can display this content. But that will someday change, and once again, they’ll be left in Amazon’s dust. But that’s neither here nor there.
My second thought on this: I can only sell an iBooks Author app version of my book through the iBookstore. I can sell my other versions just how I always have. I have a specially coded version for Nook and Kindle. I am curious, though: can I sell two iPad versions, perhaps giving them both a separate ISBN? One would be the Author app version and the other would be the “regular” version. Hmm…anyone have an answer on that one?
We’ll all wait and see what happens next in this yo-yo of an industry. The potential of this app is phenomenal, and no ambiguous EULA agreement will diminish that. If you have a Mac running Lion OS X, download the app and play around with it. Even if you don’t have an iPad. Try it out and see what could one of the greatest innovations ever in the short history of ebooks.
I’ll say it again: FREAKIN’ AWESOME.
Want to see an iBooks 2 novel in action? You can download a sample or buy Artemis Rising on your iPad. Here’s a link to the book.
Let me know what you think in the comments. And if you want to reprint this blog post, feel free. Just give me a credit.
Ooh! UPDATE: This is what might make us fall into fits of glee: an open platform ebook creator! I just heard about this less than a minute ago.
One eBook Platform to Rule Them All
A company known for long-form journalism democratizes tablet publishing.
Caveats: It’s not available yet, still in private beta, and I have no idea what it might cost, if anything.
File format contains copyrighted CSS, JS which does
the magic of interactivity. How should Apple protect it?
Apple simply wants to have unique design which is not
copyable by Amazon.
Author is written in Cocoa which is not ported to Windows.
It can be done but it is great pain to support because of Windows
API and differences between Mac and Windows.
Apple gives away software in order to sell hardware.
May be your friends can go to Apple Store to build their book
without buying a Mac.
Adobe may be able to build your mythical application.
Amazon’s format is already proprietary which they just
introduced with interactivity in September for Fire launch.
Dashcode widgets have been around since 2005. They were used
to build Dashboard widgets. a Developer will be selling what you
want very soon. Please request Apple to give you a Map widget
like iMovie indiana jonesque map or even iphoto places map.
You could use Google directly but they have changed their TOS for
free maps recently which may not be to your liking.
Thanks for reading, Laura!
Thanks, rd, for your great comments and interesting perspective! Yes! I want a Indiana Jones esque map. =) I’ll check out Google Map’s new rules just for kicks. Thanks for the tip. And I’ll send feedback to Apple, for sure. I suspect I’m one of the first novelists to get their fiction books up in this new format, so it’s interesting being a guinea pig. Wheek!
I know that Amazon has their upgraded format for the Fire, but my hope is that their next upgrade will be a complete overhaul. I want them to create a similar ebook creation app or program. We’ve all needed something like that for years. It’s about time.
I’m hopefully buying an iMac soon. I can’t wait to get my hands on this!!!!!!
Very interesting. I love the whole idea of an interactive book. Very cool!
The reason iBooks isn’t available in Mac
is because lower PPI resolution of Mac
compared to iPad (non good reading experience)
and of course licensing issues.
and also piracy.
If iPad DRM is used on a Mac, people will
be able reverse engineer it faster thus less people will
buy your book because they can monitor to see how decryptions
is happening and circumvent it on Mac.
It took 9 months to jailbreak the ipad 2.
Wow! So you’re saying the screen resolution on an iPad is superior to that on a Mac? I had no idea. I wonder why that would be. Seems counter-intuitive.
I’m not sure why you would think that that would be counterintuitive. A smaller screen needs a higher resolution in order to display text since text is often shown on the smaller screen at a smaller actual physical size. Smaller letters need a finer screen to show up clearly.
Nice review, Cheri–and it pretty well illustrates the problem some of us slower folk have with publishing technology. All those months you spent learning to code are suddenly whisked down the memory hole by a new software app–which, within minutes of the time you finish your review, is apparently about to be replaced by a even more remarkable app.
Yuppers, Tony. I can see myself using Apple’s iBooks Author app for its specialized version and Atavist’s push aggregator for everything else (if it’s reasonably priced and the initial hype is true). That’d be lovely, wouldn’t it? Even you could do it! =)
Wow. This sounds like my kind of ebook formatting. I wish it could be this simple to code for every ereader.
I found some links that might be helpful to you regarding your map wishes.
Dashcode has a map template that takes KML files and GeoRSS.
So you should be able
yes ipad has a 132 ppi. where as Mac typically uses 72 dpi
standard even though some laptop screen are higher in ppi.
iPad 3 may be 264 ppi if the resolution doubles.
Yes, as long as they have different ISBN’s, and the one that is created with iBooks Author is sold only at the iBookstore. The other iPad version, an EPUB file created with whatever, CAN be sold at the iBookstore but does not HAVE to be.
And I agree with you: the reason that, for now, the fancier books can be sold only through Apple is because those books would act like trash on any other reading device, and then who would the user blame? Not Amazon or Barnes & Noble or Kobo. No. They would bash Apple for making an app that they couldn’t get to work right.
A big part of Apple’s identity is wrapped up in a great user experience, and they take great pains to protect that. From the start of the iBookstore, if you didn’t make a well-designed book (i.e. one that worked correctly with the iBooks app and displayed nicely for the user), Apple would not let you sell it. However, they make it as easy as they can. They have always given approved iBooks publishers free examples of well-written code to use with their books, and it’s great code. (Sorry that you had so much trouble getting the video to work. It’s really not hard, once you know how.)
So, for now, books created with iBooks Author will only work with iBooks. O.K., that’s annoying to some people. But… have you guys seen them? They’re great books!