How to read a book on your phone

I’ve written a lot about ebooks over the years, but very little on what makes them readable. That’s unfortunate, since the defaults you get with almost every ebook reader provide a sub-optimal experience. Every time I hear someone say, “I tried reading a book on my iPhone, but I just couldn’t do it,” and I look at their phone, I realize that with those settings I couldn’t do it either. So let’s go over what makes books readable in the first place and how to mimic that on your reader of choice.

The first and most obvious aspect of readability is of course the typeface you use. The right font can make or break your reading experience. Fonts come in two main styles, serif and sans serif. Serif fonts have small ornamental lines, called serifs, that give them a more stylized look and more importantly, guide the eye along the line of text. It’s for this reason that serif fonts have traditionally been favored by typographers for long stretches of narrative. Common serif fonts are Times Roman, Georgia and even the monospaced Courier.

Sans serif fonts tend to be much simpler letter shapes, as they lack the serifs. This makes them look cleaner on the page or screen, but in theory less readable over time in bulk paragraphs. Sans serif fonts have traditionally been preferred for on screen use because they’re simpler to render. Common sans serif fonts include Helvetica or Arial, the Verdana/Tahoma/Nina family and the handwriting-like Comic Sans.

So what’s best for ebook readability? That’s not an easy question. It’s worth noting that most people don’t actually read one letter at a time. Instead adult readers take in whole words, phrases and even sentences at a time. The pattern recognition on the brain is absolutely crucial, and anything that disturbs or alters the expected patterns will dramatically impede the reading process. For anything longer than a few lines, I prefer serif fonts. On a good serif font, the serifs really do guide the eye along the line and make reading more comfortable. If I’m on a lower resolution device and have to go with a sans serif font, I prefer something like Trebuchet MS, which at least has pseudo-serifs to differentiate letter shapes. Verdana, which was also designed expressly for on-screen readability, as well as it’s compressed sibling Tahoma—and the even further compressed Nina—is another good choice if you need to go sans serif.

So now that we know what kind of font to use, which fonts in particular are best? While there’s a certain appeal to Times or Times New Roman, the “default” proportionally spaced serif font, it was designed to be printed, and doesn’t always translate well on screen. It’s a very narrow font with comparatively little white space between lines, to allow news papers to cram the maximum number of words on the fewest possible pieces of paper.

If it’s available, I prefer Georgia, which was designed for on screen readability. It has a taller x-height than Times, which means the lower case letters are taller—and generally wider—for a specific point size than Times.It also has lovely serifs that evoke the typesetting on vintage hardcovers and a clear, script-like italics version.

If you’re using a newer device with TrueType turned on, Microsoft’s new Cambria or Constantia fonts look even better than Georgia, because they’re designed not only for on screen readability, but also to take full advantage of subpixel font rendering. Basically, these fonts make it appear that you have three times number of pixels that you actually have. Cambria has a more “informal” feel to it, with rounder letter shapes. Constantia is closer to Times with a lot of straight, vertical lines.

Okay, you’ve got the right font, now how big should it be? This is balancing act and frankly the hardest decision to make. It’s dependent on several factors.

First is line length. A good rule of thumb is that you should have on average about six to eight words per line. So if you pick a font that’s too big, you won’t get as many words per line as you should and reading will feel very “choppy” as your eye keeps darting back and forth very quickly. (Conversely, this is why it’s important to use giant margins or split text into columns on wide monitors. If the line length is too long, your eye tends to wander up or down to other lines before you get to the end and reset.)

But you also need to have a reasonable amount of white space. A lot of reader software will allow you to set your margins. Believe it or not, there’s actually an advantage to having healthy margins around the text. It helps the brain compartmentalize the text and keeps the page from looking too busy and overwhelming. Try it. You’ll be more comfortable with a reasonable margin than with text that goes right up to the edges of the screen.

White space is also a function of font choice, as your font will tend to define, at least at first, your vertical line spacing. One of the reasons I like Trebuchet MS so much is that in addition to being a serif-like sans serif font, it also defaults to wider than average line spacing, with more white space between lines of text. This makes it easier for the eye to follow long each line without jumping above or below and confusing things. This is also why the latest versions of Word default to 1.15x line spacing. That little extra white space really makes a difference in readability on screen.

So what’s the answer? It’s going to be different for everyone. Find a serif font you like and then try different combinations of margins, font sizes and if you can, line spacing until you find something comfortable at six to eight words per line. In eReader on my iPhone, that comes to Georgia at Medium font size, normal line spacing and wide margins. On the iPhone Kindle app my options are more limited, so I just go with the second of the five font sizes. In Stanza, my reader of choice, you can tweak almost everything and I have it set up with nearly ideal font, font size, line length and line spacing.

Let’s talk about paragraphs. Most of time, you’ll take what you get. Some books and some readers will give you indented paragraphs, like you see in most printed fiction, where the line spacing doesn’t change but the first line of each paragraph is indented slightly. Others will give you block paragraphs, where the first line of a paragraph is not indented, but there is a blank line between every paragraph and the next. If you have the option, go with indented paragraphs. They’re no easier nor harder to read than block paragraphs, and they let you fit more on each page, so you turn pages less frequently.

Another point to consider at the paragraph level is justification. Here I differ with the conventional wisdom. All the studies I’ve read say to go with unjustified, or “ragged” right margins, where the letter spacing is uniform and each line ends where you run out of words and have no room to fit the next word in the sentence. The uniform letter spacing makes it easier for your brain to read each word.

In justified paragraphs, the spacing between each letter or each word is tweaked just enough so that the end of the line makes a straight vertical line down the right side of the screen just as the left margin does. Personally, I like this better, even if it makes things just a bit harder to read. It looks more like a real book that way. I find ragged margins distracting, so for my money, justified is actually easier to read. It helps if your reader program supports automatic hyphenation, breaking big words across lines if they fall at the line end. This means you have virtually no instances of the big honking gaps that can occasionally happen with full justification, big words and shorter line lengths.

Okay, you’ve got all the typography down. What about color? On a lot of phones, you aren’t limited to just black and white. Oddly enough, though, you’re probably best off sticking with black text on a white background anyway. It offers the best contrast, which is going to lead to less eye strain. If you want to mimic the warmer feel of a paper book, you can change the background to an off-white or cream color without losing much in the way of contrast. A lot of readers allow for inverted colors for night reading with the lights off, but I find that you’re probably better off just dimming the brightness to a black on gray that you find comfortable. Light text on black doesn’t look very good with font smoothing enabled. In general, I would stay away from other color combinations, and please, never, ever use a graphic texture as your background. A lot of readers allow for this, and even make it the default, but it’s just going to distract your eye from the actual text. Yes, it’s very cool that you can make the background look like parchment, but don’t do this if you actually want to read the book.

A lot of books will scroll the text for you, like a teleprompter. While this seems like a good idea, in that you can read not actually needing to turn the page, I’ve never made it work. My reading speed changes depending on the text. Pages with a lot of dialogue I’ll get too much ahead of the scrolling and get frustrated because I have to wait, and pages with a lot of description or interior monologue I’ll have to start skimming just to keep up. Stick with turning each page one at a time for maximum readability.

And lastly, we come to all the other stuff your reader program can display that isn’t the book. Things like title, page number, time, buttons for all kinds of functions: find, annotate, bookmark, etc. If you can, keep these to a bare minimum. Every additional thing on the page is something your brain has to rule out every time you see it. On Stanza on my iPhone, I have just the progress bar—a thin line at the very bottom of the screen showing how much of the book you’ve read relative to the total length—and the standard iPhone status bar at the top. I could even hide the status bar, but I usually read in bed, and I need to be able to see the time so I know when it’s time to put the book aside and go the heck to sleep if I want to avoid being a zombie the next day. Simpler is better, in general.

And that’s it! Now you know enough about typography and how the brain actually reads text to make your ebook reading experience as close to or even better than reading a paper book.

11 thoughts on “How to read a book on your phone”

  1. I agree, but I have found a solution – ereader software allows for adjusting the scroll speed ***while*** reading. Works like a charm. You can zip along at freeway speeds, but slow to a crawl when you hit a rough patch. You can also stop, page around and resume scrolling when the mood strikes.

    On a mouse-driven machine, ereader’s scroll speed is controlled by the mouse’s scroll wheel. It can also be done by using the cursor control keys (arrow up to slow down, arrow down to speed up).

    On the Viliv S5, it’s done by using the scroll stick.

    All of your other comments and suggestions are dead on, there are numerous adjustments to be made, depending on screen size – and the smaller the screen, the more adjustments you require.

    A note about contrast, I tried black text on off-white, but have gone to black text over very light blue-grey background at the lowest brightness settings – this works very well for me in low-light situations.

    Thanks for a heckuva post !

  2. I’m a bit perplexed by the advice you give, considering that with regard to font, line length, ragged margins, indents, and so on, your blog follows none of it. Reading is reading. And most of us are reading sans-serif fonts all day, with long line lengths, ragged margins, and white space between paragraphs rather than indents.

    I find that the default settings in Stanza and the Kindle app on the iPhone are both pretty good. I find myself quite happy reading either. Many of the books aren’t well formatted, but a lot of print books aren’t well formatted either.

    My experience is that people who say “I could never read a book on an iPhone” have actually just never tried it. It’s in the same class as all the comments from people who say “who would read blogs; I don’t want to hear about someone’s cat”, or more recently, “what’s the point of twitter; I don’t want to hear about what you had for lunch.”

  3. jeff-

    you’ve laid out a pretty good path of questions
    that people should ask themselves to answer…

    unfortunately, you suggested what their answers
    should be, according to your _own_ preferences.

    i find that, when having people choose the best
    font for themselves, they don’t have any problem
    doing that. you suggest the best choice will be a
    serif font, but i’ve found that roughly half of the
    population will disagree with you on that matter.

    likewise, you suggest a measure of 6-8 words,
    which then sets the font-size, but i’ve found that
    it’s best to let people choose their own font-size,
    regardless of how that choice affects the measure.

    i agree with you that “healthy” margins are nice, but
    i’ve found that people disagree on what that means.
    so once again, it’s best to let ’em make the decision.

    as for leading, i find that people usually have a solid
    idea about what constitutes “too much” and “too little”,
    and will quickly and easily converge on their choice…

    ditto with block-paragraphs versus book-indentation.
    the user-preference usually comes quickly and easily.

    and again with justification. some people like it and
    others don’t, so just let them decide for themselves.

    as for hyphenation, their are other considerations here.
    first and foremost is whether the hardware can handle it.
    and even if the hardware can, often the software cannot.
    plus, you need to consider if the software is sufficiently
    advanced to do its searches without hyphenation glitches.

    getting back to personal preferences, though, you tell
    people what they should be doing, based on what _you_
    prefer, when it comes to font color and background color
    (and textures), when the truth of the matter is that they
    should do what makes reading easy for _them_, not you.

    in particular, you imply that _high-contrast_ is the best,
    especially in terms of avoiding eye-strain. but many find
    that a high contrast causes them the _most_ eye-strain!
    suck people like dark-grey type on a cream background,
    and who am i (or you) to tell ’em differently? who indeed?

    like you, i’ve not been able to make scrolling work for me.
    but i’m sure not gonna argue with someone who _has_…

    likewise, i find it ironic that you advise that people should
    eliminate all the background buttons, but then you admit
    that you leave the progress-bar on, as well as the clock…
    you have good reasons for doing that, i understand well,
    and i suppose that other people would have good reasons
    for leaving on whatever paraphernalia that they leave on.
    and again, who are we to argue with them?

    again, as i said at the outset, you’ve given people a great
    checklist of items to consider. i just wish you wouldn’t
    have tried to fill in that checklist for them. they can do it.


  4. Thanks, Tim. I agree that the biggest impediment to getting people to like ebooks is getting people to try ebooks. But I also think typography matters, and can make a big difference in the reading experience.

    Good call on my blog typography. I've tweaked the CSS in my theme (along with installing a typography plugin) to bring my blog more in line with what I consider optimum readability.

  5. Wow, typography is a lot more personal than I expected. I just want to get people thinking about typography. My "preferences" as you put it, are based on lots of research (done by others, but I can read their findings) into on-screen readability. These are best practices, but they're certainly not law. If something else works better for you, great, go with Kosh. I'm just trying to point people in the right direction and most importantly, clue them in that they don't have to stick with the defaults if they find that an unsatisfactory experience.

  6. jeff-

    i've seen the research. most of it is old,
    and little can be described as well-done.

    besides, it's based on the notion there
    is one (and only one) "correct" answer.

    it's entirely possible half the population
    finds one thing to be "more readable"
    while the other half finds another to be
    "more readable", never the twain to meet.

    nobody even really _defines_ readability
    in a way that seems satisfactory to me…

    reading speed is a non-starter, to my mind.
    and reading comprehension is far too hard
    to measure reliably. retention is important,
    but needs to be measure in the long-term,
    not on a 1-minute versus 10-minutes way.

    "comfort" seems to me to be the best one,
    and who better to gauge how "comfortable"
    a person is than that very person themself?

    so personal choice is the rosetta stone here,
    as far as i'm concerned, and since choice is
    completely compatible with e-books, why not?


  7. […] those that want something to put on a shelfor dont take my advice about how to read ebooks comfortablyIll also be publishing each book via either Lulu or CreateSpacehavent decided […]

Leave a Reply

Your email address will not be published. Required fields are marked *