The Amazon Kindle, for a while the prominent way to read e-books, it looking more and more archaic as the months pass. With Apple's release of the iPad, which has already sold well over 1 million units in a few short weeks, the Amazon Kindle, with it's colorless e-ink display, looks less and less like attractive in the age of tablet computers.
We now have reports that Google is working on an android powered tablet device with shall be released in the 3rd quarter of 2010. Basically, the Amazon Kindle is a one trick pony. Yes, the power sipping e-ink display has dual benefits of last a long time throughout heavy use and also being easy on the eyes, it costs nearly 60% of that of an iPad, thus Apple should definitely take market share away from those interested in the Kindle or other e-ink one trick ponies.
Amazon is surely aware of these problems, however, as they have a popular Amazon Kindle iPhone, iPad, and iPod Touch application, which is designed to sell their books on a multitude of mediums.
In other words, just as we have seen with other technology (think the stand alone MP3 player), the Kindle is a stand alone book reader that does one think only. Apple's stand alone MP3 players do not exist anymore (other than the shuffle) with even the iPod classic model able to play video content. Therefore, Apple has even evolved.
Amazon is probably betting on the newest versions of improved e-ink displays which offer color screens and some web functionality, but again, these screens are slow, have poor viewing angles, and are NOT backlit.
We predict that Amazon's Kindle will not stand the test of time with the age of tablet computers here to stay.
Comments
One Response to “Why Amazon Kindle Sucks”
Leave Comment
“Yes, the power sipping e-ink display has dual benefits of last a long time throughout heavy use and also being easy on the eyes, it costs nearly 60% of that of an iPad, thus Apple should definitely take market share away from those interested in the Kindle or other e-ink one trick ponies.”
Instead of “thus” you should’ve written “despite this.”