Screenshots in Safari just captured the FOUT (http://paulirish.com/2009/fighting-the-font-face-fout/). Not sure I'm totally convinced about those IE8 + IE9 screenshots - I've tested those and 9 is pretty good, 8 is a bit lame and anything below 8 is appalling. What version of Windows was that?

It really takes the fun out of a project like this to make it not die in IE.

I just looked at in on a Win7 VirtualBox machine running IE 8 and it looked like the Litmus screenshot. I am convinced it looked bad, not surprised, but certainly sad :(

Yeah the timer is a bit crude, working on a better script which considers an interaction as a click, scroll, or keydown and sends minimal events to GA.

Your methods on fixing the click delay are interesting. What was your resulting click time?

I'm not an expert on this but you seem to be using a lot of javascript for your UI when most of it can be done with CSS and applying/removing classes. The JS is fine for desktop browsers but it can be really laggy on mobile (even 3GS). I think that's one of the things about jquery mobile—it uses css where possible. That said, it seemed a little unrefined for me too and I've always left it out.

I did much the same stuff (ui-wise) as you very recently, but used -webkit-animation to do most of the work which means you can also use -webkit-animation-fill-mode <-totally awesome: http://developer.apple.com/library/safari/#documentation/app...

Also, you should use the 3d versions of translate, scale, rotate like translate3d(x,y,z) because it utilises hardware acceleration (on iOS at least). Makes a massive difference. Put down the javascript stick. :-)

One media query and one stylesheet for mobile browsing/commenting. I'm happy to do it in an evening for you. Relevant post: http://news.ycombinator.com/item?id=2152372

I've written for screens smaller than 480px. I have an android that, landscape, is 860px or something. In that case it won't work, and I'd rather not make the assumption that it's a mobile screen.

I presume your android is larger than 480px and that's why you say this?

It is, but the page is unwieldy and overly wide on that browser.

Looks like there's a big gap between "small screens" and "screens that can comfortably display the page".

I guess my point to this was to show how simple it is to tailor a website to mobile webkit users. For example, HN isn't using any media queries and in probably 30 minutes it could be perfectly nice to read and respond to comments on my phone.

I'll volunteer an hour to do it.

Is there any way to have custom css files inserted into the Android web browser? Then we don't need to ask pg et al. To do this, we can do it ourselves.

Possibly, I'll have a look. Seems a very long way around for a tiny benefit. Maybe I'll try asking pg and see if it's gets anywhere.

I would be very interested if this is possible. It could be used for different sites aswell, not just HN

A mate of mine just said it would be possible for firefox on android via a plugin, but he didn't think so for the standard webkit browser.

Thanks lenary, I guess that'd be fine for a small amount of adjusted styles for mobile. Becomes a bit of a mess pretty quickly though.

I agree. It's a good idea, and I can see it having advantages over your competitors, but those advantages are negated when hard to access. UI needs to be cleaner and following all expected conventions (this isn't a new UI).

Is there a reason the landing page is 730px wide? It feels like everything got crammed in pretty hard.

I'm excited about what this could do, but it needs some time on the design before I'm comfortable playing around with it to evaluate properly.