What are the (current) hurdles in implementing and running Mobile Ajax applications?
The biggest obstacle is the same as on the desktop: browser support. With more browsers than on the desktop and bigger differences in their support for web standards and technologies required by Ajax this poses a real problem and has kept many developers from going any further than initial tests. Another technical problem is HTTP latency. Loading only parts of the website in a mobile web application can take as long as loading the whole page (still traffic and rendering time in the browser will be smaller). This varies from one connection type to the other and can also be influenced by the carrier’s implementation of their proxy. Also power consumption and battery drainage of Ajax applications can be an issue. If an Ajax application constantly connects to a web resource, e.g. to check for new data, this will not only drain the phone’s battery heavily, but may also incur expensive data fees for some users. So Ajax functionality has to be applied in a responsible and meaningful way, espe
