While they mention the latter, e-Ink model would be 'backlit' it would be front-lit (as it's been said that e-Ink can't be backlit) - using a technology Amazon bought when they acquired a company specializing in this about 1.5 years ago -- see the April 2012 article on that. There was word about a delay in July.
The Verge's Bryan Bishop points us to the full ad showing multiple devices, posted in a non-public area at Youtube by Daniel Marchena.
Got back from a late dinner near Santa Monica, so this news has been out for a few hours.
In the 2nd half of the ad, The Verge mentions what looks like a verrry large tablet at first (it would be larger than 10") but it has a hinge at the bottom and the people are using it with a keyboard and at times a mouse, so it's probably a laptop. (I'd love it if Amazon suddenly came out with a laptop).
Or even a verry large tablet :-)
At marker 0:33 or so, the hand-held tablet, at an aspect ratio of 4:3 or so, looks large as a result, relative to the current Kindle Fire, which is longer but narrower (good for HD-widescreen videos) -- it almost looked as if it could be a 8.9" one but otherwise seems just a wider 7" Kindle Fire this time, as has been expected from early sources.
Amazon smartphone?
The Verge's Nilay Patel, moreover, says that the Amazon phone is 'confirmed' and could be announced Thursday morning. Patel says "multiple sources" confirmed Amazon "is working on a smartphone that runs a variant of the Kindle Fire's Android-based system," and they hear now that the device will be "shown to the press" in the morning, although it's "currently unfinished." As with the Kindle Fire, Amazon would be using Nokia's mapping technology rather than Google's.
The Sept 6 Press Conference in Santa Monica
As an individual, I won't be live-blogging, as the big-boys have teams and some excellent technology for that.
For monitoring live blogging, I normally watch a combo of CNet, Engadget, and Gizmodo and of course we'd add The Verge now.
I'll tweet, though, some of the points that really strike me while at the event and tweets will be readable at http://twitter.com/kindleworld (no refreshing is needed, or it tells you to 'click' when there's something new).
An alternative for seeing any of my tweeted info will be to read them through the more detailed http://tweetree.com/kindleworld.
I plan to jot a few notes here on the blog as it goes, which won't be seen until you refresh or reload the screen but will do a full write-up later in the day of what I saw and heard and give it a bit more context when combined with what we know about the details of current Kindles and what the changes are relative to expectations, hopes, dreams :-)
I also hope to have a few interesting photos as well.
For daily free ebooks, check the following links:
| Temporarily-free books - Non-classics USA: by: Publication Date Bestselling High-ratings UK: PubDate Popular The Kindle Daily Deal What is 3G? and "WiFi"? Battery Care Highly-rated under $1, | Most Popular Free K-Books U.S. & Int'l (NOT UK): Top 100 free UK-Only: Top 100 free USEFUL for your Kindle Keyboard(U.S. only, currently): 99c Notepad 1.1, 99c Calculator, 99c Calendar, |
*Click* to Return to the HOME PAGE. Or click on the web browser's BACK button
No comments:
Post a Comment
NOTE: TO AVOID SPAM being posted instantly, this blog uses the blogger.com "DELAY" feature.
Am often away much of the day, and postings won't show up right away. Posts done to use referrer-links may never show up.
Usually, am online enough to release comments within a day though, so the hard-to-read match-text tests for commenting won't be needed this way.
Feedback and questions are welcome. Thanks for participating.
Technical Problems?
If you're having problems leaving a Comment, Google's blogger-help asks that you clear the 'blogger.com' cookies on your browser's Tools or Options menu bar and that will fix the Comment-box problems (until they have a permanent fix).
IF that doesn't work either, then UNcheck the "keep me signed in" box -- Google-help says that should allow your comment to post (it's a workaround to a current bug).
Apologies for the problems.
TIP: There's a size limit. If longer than 3500 characters or so, in a text editor, make two posts out of it.