Results tagged “kindle”

Kindle Voyage

By Michael Mulvey on November 5, 2014 10:27 AM

It seems Amazon wants to blanket the world in cheap Kindles, not great Kindles. Not surprising.

Marco Arment on the Kindle Voyage:

And this crisp, new, high-resolution screen is still displaying justified text with very few, mostly bad font choices. Some of these choices, like the default PMN Caecilia font, made sense on the old, low-resolution Kindle screens but need to be reconsidered for this decade. Some of them, like forced justification and forced publisher font overrides, have always been bad ideas.

But Amazon doesn't care. Nothing about the Voyage's software feels modern, or even maintained. It feels like it has a staff of one person who's only allowed to work on it for a few weeks each year.

If you're making devices to read books on and you don't give a shit about typography and readability, then what do you care about?

It's like a car maker not caring that their tires are lopsided and their seats have no cushions.

Oh, and Bryan is still waiting for page scrolling on the Kindle app for iOS.

An Update on the Kindle Update, Updated

By Bryan Larrick on June 10, 2014 10:26 AM

Kindle version 4.3 was released today, and it has some great features, including the ability listen to audiobooks directly in the app. But...does it have scrolling view yet? No, it does not.

First-Sale Doctrine Ain't In Effect, Yo

By Michael Mulvey on April 30, 2014 11:35 AM

Joel Johnson from NBC New on the licensing around digital purchases from Amazon:

The core issue might actually be a simple matter of semantics: when we click a digital button that is labelled "Buy," we expect that we're actually buying something. But we're not buying anything, we're licensing it. Just last year, the Supreme Court ruled that the first-sale doctrine does not apply to software -- or e-books. Or apps. Nor pretty much everything you "Buy" online that doesn't get shipped to your home in a cardboard box.

The perpetual tug-of-war between content wanting to be free and companies trying to lock it down continues.

An Update on the Kindle Update

By Bryan Larrick on April 25, 2014 6:49 AM

Kindle for iOS, version 4.2 was released the other day. New features include easier access to the table of contents of books, and something called X-Ray Smart Look-Up. It's a welcome addition, actually. But, has continuous scrolling, one feature that has been missing for years, been added yet?

No, it has not.

The New Kindles

By Michael Mulvey on September 6, 2012 2:53 PM

Very smart and interesting developments happening right now at Amazon's Kindle Event in LA.

They're clearly putting a lot of thought behind what reading and video-watching experiences should be (and taking advantage of their properties like IMDB in interesting ways).

But the realization I'm left with is that Amazon (still) sees the tablet primarily as a consumption device. Yes, they include Exchange email support and calendar integration, but those are secondary. Perhaps this consumption focus is due to the fact that not only do they want to sell their own content, but also because they've forked the Android operating system and thus can't guarantee Android applications (ones for productivity, not consumption) will work on it.

It will be interesting to see how well these new Kindles do in the market.


By Bryan Larrick on September 2, 2012 1:38 PM

The latest update (3.2) to the iOS Kindle app is out, and it is steadily improving on the iPad, although in incremental steps. The most significant change iPad users will see is the introduction of changeable margins, mirroring a feature already present for Android users. Users can now select between three different options, illustrated below:


The first option, on the left, is close to the margins in the regressed update I covered in June, but there is a more comfortable amount of white space above and below the text. It's a little crowded, but much easier on the eye than the blocky mess from the end of spring, which caused howls of protest on the app's store page.

The best readability comes with the other two options. The second option is identical in width to the July update, with the text moved up slightly, while the third has left and right margins identical to that which was banished in the June update, with the leading opened up some. All in all, these three represent fine options for a user to choose from. In the future, it would be nice to see the app incorporate different fonts. The iBooks app, Apple's answer to Kindle, lets a user choose from seven different fonts, while Stanza, the now unsupported reader app that Amazon owns, lets the user choose from all the system fonts that were available at the time of its final update in 2011. Once again, it boggles the mind that Amazon has a readily available reader app that is better designed and continues to draw nothing from it, that a user can see, at least.

Another feature from Stanza that I love is the ability to change the brightness of the screen with a finger swipe, rather than having to go into the options menu. It's great for maintaining flow while reading. Curiously, the new Kindle update touts improved brightness controls, but what they seem to have done is lock the brightness with the iPad. That is, if a user changes the brightness controls within the Kindle app, it changes the brightness across the entire iPad, not just within the app. This is very odd.

Still, Kindle version 3.2 for the iPad is keeping pace with reader apps in general, as they go through the long process of becoming viable alternatives to printed books. Presentation is key. As soon as all reader apps figure this out, users will benefit greatly.


By Michael Mulvey on August 16, 2012 8:56 PM

US State Department cancels no-bid Kindle contract

Prior to payment and delivery, the US State Department has torpedoed its $16.5 million contract with Amazon, proposed in June, for Kindle e-book readers. The contract is headed to a normal Request for Information process, rather than the no-bid award that Amazon was initially selected to fulfill. The program was intended for use in overseas language programs, and any device chosen would have to support wireless connectivity, central management, text-to-speech, long battery life and a number of other requirements.

Translation: the US State Department realized the Kindle sucks.

Next time, Amazon. Next time.


By Bryan Larrick on July 9, 2012 12:17 PM


After howls of protest in the app store from users, Amazon walked back some of the changes it made to Kindle for iPad. Seen above are screenshots from an update Amazon released to the app store last week. The margins surrounding the text that had been eviscerated in the name of readability have been somewhat restored. However, the new, intrusive toolbar interface remains. The user reviews that the previous update had gotten are doubtless behind the changes, showing that companies do indeed respond to heavily negative feedback from customers.

In reading those customer reviews, there is nary a review that praised the narrow margins of last month's update. So Amazon changed it. But there were also hardly any reviews that were critical of the toolbar, so Amazon left it as is. Make no mistake, the current toolbar is a downgrade compared to the previous iteration, but it was saved because the new margins were so atrocious that users completely missed the toolbar. Mediocrity is invisible when it stands next to hideousness. Next, Amazon is going to have to figure out how to keep the app from crashing.

Improved Reading Experience? No.

By Bryan Larrick on June 18, 2012 2:44 PM

Last week, Amazon updated it's Kindle app for iOS. For the iPad, the new update is a case study in poor design. From the update blurb in the app store:

Improved reading experience on iPad: Smaller margins and a cleaner look help you focus on the author's words.

When I first saw this in the blurb, I was immediately suspicious. It's hard to overstate the importance of healthy margins and whitespace in good design. Generally, it's also one of the earlier casualties when good design meets project managers and clients who aren't designers. But I updated the app anyway. Upon opening, I saw what had been a decent treatment of margins had been destroyed by the redesign:


The image on the left is a screen capture from an iPad without the update installed (I'm a developer, I have more than one iPad. How first world of me.). The image on the right is with the update installed.

The smaller margins do indeed help a user focus on the words. In fact, that's all a user can focus on. What Amazon has done is create a solid mass of text that has no breathing room. It's claustrophobic. It's stressed. It's like standing three feet in front of a brick wall and pretending you're appreciating the architecture of a building.

The words are the most important aspect of a book. That's intuitive. But, presentation is very important. Having ample margins helps the eye flow over the text and makes it easier to move from one line to the next while reading. Making the margins smaller in the app hinders the ease with which the eye can move over the page, making the book harder to read, not easier. Also, it's just ugly.

There is also a usability gap that was created with the update. Previously, the app's toolbar overlays would not interfere with the text on the page. Some people like to read with the toolbar visible. I'm not among them, but I respect that. After the update, keeping the toolbar visible is no longer a workable option:


Also, the new toolbar design has none of the nuance of the previous version. It's black, bold, and in a user's face. Even if it didn't cover up text, the look and feel of the new toolbar is a downgrade.

The Kindle app in the iPad has been a conundrum ever since I began to use the device, simply because the presentation has always been suspect. The options for reading have been limited in ways I could never understand. First, there is only one font. This is an inexplicable omission. Currently, there are over fifty font families on the iPad. Limiting the user to only one makes little sense. In apps where content is coming from a single source, one font does make sense. The New York Times app has only one body font they use in their articles, but that font is part of their brand identity. Not only that, The Times is the source for the vast majority of the content they feature. But with Kindle, most, if not all, content has been created by other sources. Just like you would never expect every book one buys from a brick and mortar store to have the same font, no user should expect that limitation to exist on their digital devices.

Secondly are the options for font size. In the Kindle app, there are six font sizes available, from laughably small to big enough for my grandmother to read without her glasses, with little variation in between. The above screen captures are using font size number 3. Here is a side by side comparison of font size 2 and 3:


The difference between the two sizes is quite large. A little more variation would be welcome.

As it happens, there is no reason for Amazon to have a clunky, poorly designed reader app on the iPad. The first reader I ever installed on my iPad was Stanza, a free app originally developed by Lexcycle, a company subsequently purchased by Amazon in 2009. Stanza's interface while reading is beautifully designed. The margins are good, the themes on the page are more varied, a user can choose any of the font families installed on the iPad, and the distance between font sizes is much more flexible:


Stanza provides a much more pleasant reading experience compared to the Kindle app. But, Amazon has chosen to kill Stanza, releasing a single update for the initial release of iOS 5 with no more forthcoming. Amazon has the means to make a reader app with good design. They have chosen not to.

It's still early in the digital reader game. Publishers and typesetters have been working on design for centuries, while the Kindle has only been around for five years. Apart from design, there are problems with formatting and editing that still need to be improved to make readers better than a printed book. Right now, readers win on convenience, and not much else. Going backwards isn't helping.


By Michael Mulvey on September 28, 2011 10:29 AM

Influencer: Steve Jobs announces the iPhone, January 2007


Influenced: Jeff Bezos announces the Kindle Touch, September 2011



Daily Exhaust is hosted by DreamHost, powered by Movable Type with Minted statistics.