Hacker News Reader

Would be nice to hear tips specific for mobile browsers. My site is going to be accessed mostly from mobile browsers (over edge/2G connection most of the times). No images only data. This is what I have decided to follow:

1. Make it ajax as much as possible to avoid sending requests for each operation. Try to keep everything in one page dashboard. 2. Keep the page/services sizes under 1500 bytes (Ethernet)

View on HN

As a user who sometimes has terrible coverage and 2G I would suggest not using AJAX so much. If you do, make sure it is cached by the browser. It is incredibly frustrating to have zero indication if there is some AJAX loading going on in the background or not. The browsers don't show and animated indicators that websites show, well, like to animate for eternity. And if loading stopped or you decide to reload the page in the hope that this time it will load better, sites usually fetch the whole shebang again.

So my recommendations: Make sure your site is split into nice, cachable chunks (css, images, js, etc). If you can, avoid JS. Avoid loading content invisibly to the user in the background.

How does using ajax avoid requests? Partially updating a page usually results in many (but smaller) request. Unless you have good framework, updating multiple parts in one request can get complicated.

Reply on news.ycombinator.com