Honestly, I think this is way more effort than it’s worth.
First of all, most ‘normal’ users simply couldn’t care less about the 40px or so that the address bar takes up.
Secondly, most users won’t wait for the page to finish loading before they start browsing it. The number of times I’ve scrolled down half a long web page before it’s finished loading, only to be zipwired back to the top after a few seconds. It’s infuriating. I can understand the desire to make the site more immersive and content-focused, but is all this effort really going to pay off? You’ve got a lot of JavaScript to work around 40px of OS chrome, as well as some tricky UA sniffing for Droids etc.
In my opinion, it’s certainly not worth the effort.
Dan Eden
Honestly, I think this is way more effort than it’s worth.
First of all, most ‘normal’ users simply couldn’t care less about the 40px or so that the address bar takes up.
Secondly, most users won’t wait for the page to finish loading before they start browsing it. The number of times I’ve scrolled down half a long web page before it’s finished loading, only to be zipwired back to the top after a few seconds. It’s infuriating. I can understand the desire to make the site more immersive and content-focused, but is all this effort really going to pay off? You’ve got a lot of JavaScript to work around 40px of OS chrome, as well as some tricky UA sniffing for Droids etc.
In my opinion, it’s certainly not worth the effort.