They must be able to highlight key passages and leave notes in the book. They must be able to search in the contents of the book. They must be able to move around in the book, including navigating its table of contents. They must be able to open a book and read it. That said, all of these products must provide a basic set of functions for users to experience them as “Kindles.” That set includes, at a minimum, giving users access to their book library. As a result, Kindle’s user interface is different on each platform. In some of these platforms you can peruse and buy from the Kindle bookstore, while you can’t do so in others. The Kindle apps on other platforms, such as Windows and iOS, are also optimized for reading books, but run in the context of a third party’s operating system. Dedicated Kindle e-ink readers (such as the Kindle Oasis) are optimized for reading books.
And so on.Īlso, even though they’re all labeled “Kindle,” not all Kindle products have the same capabilities. Some have color displays, while others are monochromatic.
Some have touchscreens, while others use a mouse or trackpad. These devices don’t have the same features and capabilities. Alas, this variety also presents design challenges. It means you can read your e-books on your preferred device.
This widespread availability is one of the system’s most attractive features. Besides dedicated devices, Kindle also encompasses apps that run on other hardware platforms, such as Android phones, iPads, and personal computers running Windows and macOS. Over the years, the line has grown to include several devices with different capabilities, ranging from relatively simple readers with e-ink screens to fully-featured tablets. The Kindle product family started with a dedicated e-reader device in 2007. One of my favorite examples is Amazon’s Kindle. But it’s even more challenging to maintain coherence within a family of products. It’s challenging enough for a product’s conceptual models to be internally coherent.
0 kommentar(er)
