Quite simply, this is hysterically ugly. Via Niclas Bergström.
Update: Via Matt Zanchelli, this appears to be an internal build icon used unintentionally. You can see it at the 31:24 timecode of this developer video, ironically in a section of the presentation devoted to differentiating between an internal build and a release build.
In March, the New York Times unveiled a major redesign of individual article pages. The company billed it as an interpretation of the newspaper for the online experience of 2013, replete with a requisite responsive design, web fonts, and bigger photography. In addition, the newspaper eschewed pagination in favour of a single-page format.
I received my invitation to test the prototype earlier today. In the email, the Times promised that this redesign was “optimized for iOS 6 on iPad”, which is an oddly-specific targeting. However, it speaks volumes about the shifting device demographics. The website for one of the most widely-circulated newspapers in the world is primarily targeting iPads — not desktops, not laptops, and not “tablets”. That’s huge.
But a focus on a contemporaneous website doesn’t necessarily translate into a successful web experience. It’s important to keep in mind that this is just a prototype, and is very much a work in progress. But, as of right now, it requires a lot of work in order to progress:
As you can see from the video, the article page uses its own crappy scrolling coefficient. It feels too fast and inconsistent. A visit to the WebKit Inspector reveals that the article resides within its own hidden overflow div which has some scrolling Javascript applied to it. This decision allows the Times to provide navigation between articles by scrolling to the left or right. One side effect of this implementation is that it breaks the native gesture to jump to the top by tapping the status bar. For an experience ostensibly optimized for iOS 6 on an iPad, this is shockingly poor.
A couple of other issues were immediately noticeable: the lack of scrollbars is presumably another byproduct of the odd scrolling implementation, and graphics throughout the prototype are not optimized for a retina display. Finally, the prototype doesn’t work at all on my iPhone.
I must stress that this is obviously a prototype, and doesn’t (yet) represent the shipping product. However, the Times is releasing these early previews in an attempt to solicit feedback and issues. I’m only too happy to oblige.
Zach Epstein, BGR:
The HTC First, or “Facebook phone” as many prefer to call it, is officially a flop. It certainly wasn’t a good sign when AT&T dropped the price of HTC’s First to $0.99 just one month after its debut, and now BGR has confirmed that HTC and Facebook’s little experiment is nearing its end. BGR has learned from a trusted source that sales of the HTC First have been shockingly bad. So bad, in fact, that AT&T has already decided to discontinue the phone.
More like HTC Last. Am I right, ladies?
Clay Bavor, of Google:
Life gets a bit easier when your Google products work well together—whether that’s inserting a Drive file into an email or sharing a photo from Drive on Google+. As this experience becomes more seamless, separate storage doesn’t make as much sense anymore. So instead of having 10 GB for Gmail and another 5 GB for Drive and Google+ Photos, you’ll now get 15 GB of unified storage for free to use as you like between Drive, Gmail, and Google+ Photos.
Very smart update. The great thing is that if you don’t use Google+ or Drive, you now (theoretically) have 15 GB of Gmail space.
