Google eBooks have landed and with them a slew of desktop and mobile apps. Earlier today I tweeted about my disappointment with eBook typography, and thought I should expound on that comment.
With the iPhone 4 as my test-bed, I decided to compare the three major iOS eBook apps – namely iBooks, Kindle and the newly fledged Google Books. Because of its small screen size the iPhone isn’t an ideal book reader, but I do use it as such and I believe the arguments hereunder will apply to tablet and desktop readers equally well.
The iPhone 4’s Retina Display truly is gorgeous. Fonts on screen have never looked better. But typography is more than just fonts. In books it is the subtle art of making a page read well allowing the reader to truly become immersed in the words themselves.
In order to fairly test the differences between each app I started with a configuration that is common to all three: white background, full-screen, vertical mode (Google Books has no horizontal mode) and medium-size Georgia. For content, I chose one of my favorite plays – The Importance of Being Earnest by Oscar Wilde. Because of the ample stage directions, this eBook stresses many key difficulties in typography.
I’ll start with what I think of as the reigning champion of eBooks on iOS. Amazon has an excellent library that seems to be improving every day, and upon the its first release the app showed promise of becoming a great reader.
Kindle was the only app in which I actually purchased The Importance of Being Earnest. Both iBooks and Google Books provided a free public domain edition, but at $1.43 the Kindle price seemed at trifle. I did wonder, before buying it, whether the cost would be justified by particular efforts in the digitization of the book. I found none.

What is most apparent in the Kindle app is the balanced and thorough use of real estate. At such a small screen-size every pixel counts and Kindle does a good job. The text is well padded and seems to fully fit the screen. We even see hyphenation! Unfortunately the justified text creates awkward spaces especially around the word “sandwiches” in the example above.
Why is hyphenation important? Hyphenation is essential, especially on the iPhone because it allows text to fill the page without resorting only to justification which tends to create these “rivers” in the text – columns of white space that detract from the words (see exhibit A).
Character introductions and stage directions in Kindle are simplistic in their styling. Not awful but we can do better.
iBooks is Apple’s default book reader, I didn’t have any trouble finding The Importance of Being Earnest as a free public domain edition. We know that iBooks hasn’t lived up to Steve Jobs’ legendary love of type. In fact, the first release’s justified text was so blatantly unreadable that pundits such as Khoi Vinh and Stephen Coles cried calamity. Since then, Apple has improved the app significantly by adding left-alignment. Still, hyphenation is not to be found.

What we first notice, especially in comparison to Kindle, is the number of extraneous elements present in full screen mode: status bar at the top, title of the book, page number and graphic cues left and right of the text. In my opinion all of these are unnecessary and impede on the available real-estate.
It is also important to note that protagonists are presented in bold rather than uppercase. This may work well in horizontal mode, or on the iPad, but in this case it create imbalance in the flow of the page especially when combined with disproportionately large indents. As we will later see, small-caps are the traditional solution for introducing characters. In lieu of small-caps, bold may work better than all-caps but only when given enough room to breathe.
With Google Books, finding The Importance of Being Earnest was no trouble either, and like iBooks was available for free.
The contender enters with a new addition – italic stage directions – and excellent use of short indents to delimit paragraphs. The left-aligned text is welcome, but lack of hyphenation often creates imbalance. The page number at the bottom seems extraneous especially because it provides no context (page 20 of?).
Google Books could certainly use more comfortable and even margins around the text, but it is almost on par with Kindle.

Interestingly, Google provides the option of seeing the scanned page. While this isn’t of great value on the iPhone screen (it’s just too small to read), it does give us insight on what a page from a book can really look like.

Here were are introduced to a new form of styling: small-caps. I urge you to read Alec Julien’s excellent column on small caps at I Love Typography as it will explain their subtlety and importance. Simply put, small-caps are small versions of capital letters which have been recreated to evenly match the weight of their counterparts. They are often used for acronyms, headers, captions and character introductions in books and magazines to keep a consistent ink density throughout the page (aka color).
This piece wouldn’t be complete without a proposed solution for Apple, Amazon and Google to work from.
Successful eBook typography (much like traditional book typography) will require the following:

Maybe not perfect, but better.
eBooks may never reach the level of typographic finesse that their paper counterparts did, but I don’t see why they can’t. In fact, I hope eBooks will become works of beauty worthy of the ages.
Because most styling can be automated fairly accurately – as demonstrated by all three apps – typographic perfection in eBooks will depend on how carefully we craft the rules of this automation rather than the antiquated and painstaking process of balancing each page by humanly caring for each hyphen.
So what are we waiting for?