Gawker’s Gulp Moment: Big Redesign Is Driving People Away | Hacker News Reader

Gawker’s Gulp Moment: Big Redesign Is Driving People Away

techcrunch.com

24 pointsandre3k114 comments

It drove me away. Besides the horrible readability of the site now, my main method of news surfing (middle clicking on anything that looks interesting, and then going through each of the tabs one by one) no longer works on gawker sites.

I never realized how enslaved I was to gawker (kotaku and lifehacker to be precise) until I stopped reading them. The amount of free time I have now (to waste on HN) is astounding.

Part of the catastrophic drop may have been google referrals. I've noticed in the past with old sites if you do a dramatic upgrade on them, google recoils a bit and starts re-indexing. i've seen search referrals take up to six months to completely rebound. The big shocker here is if google hits their homepage, it's met with a big "fuck you". I knew they were doing "shabang" but didn't realize they had zero fallback for no js.

The SiteMeter graph is telling. But the Quantcast graphs, on which this article is hanging its hat, say nothing at all. The author appears to have misinterpreted the graphs without first looking up the concept of "overfitting".

The SiteMeter graph is irrelevant too as they didn't add the SiteMeter.js.

Nice hack to get the old Lifehacker and Gizmodo back:

http://ca.gizmodo.com/

http://uk.gizmodo.com/

Works exactly the same for lifehacker. The new design, apart from it's disorienting scrolling behaviour, it's also very inefficient in terms of using screen real estate well. Impossible to quickly scan articles and determine which ones are worth reading. Fortunately you don't even need to see the ugly redesign.

The new layouts for both gizmodo & lifehacker seem quite buggy to me (Mac, latest Chrome). Most obviously, there is a grey line that tracks its way up the screen as I scroll past 'the fold'. And I agree with earlier posters: user test before release (qualitative), and split test as part of the release (quantitative).

If you tried RSS and were frustrated with the previews of their posts, try their full feed: [Gawker site].com/vip.xml

Silver lining: I discovered m.gawker.com.

Unfortunately, I discovered this by trying to find an article I had once read (about the effects of caffeine usage) by doing a Google search on my iPhone and then clicking the link, which detected I was on an iPhone and redirected me to m.gawker.com (or m.lifehacker.com or something like that), throwing away the hash URL and putting me at the root of the site. As there is no safe way to do a 302 redirect with a hash URL this strategy is doomed to fail.

Aye, and I thank Penny Arcade for that one. Even so I only hit kotaku once or twice a day now instead of practically leaving it up, which is probably good for me.

It's the oddest thing. I thought the gawker redesign was specifically targeted at the iPad. When I opened it up on the iPad, I got the WAP-like text interface.

Weren't the sites down for a while too due to JS problems?

The most important lesson that can be learned from this is: split test everything.

Could this also be related to how data is reported to Quantcast? Many of what used to be page loads are now AJAX requests - and the page loads on Quantcast may have recovered after they added API calls on notify Quantcast.

Reply on news.ycombinator.com