For the past year or so, I’ve noticed that my Facebook mobile apps have slowed down with each screen tap.
I’m not sure when that behavior started, but it’s quite annoying and happens on both my Android (s goog) and i OS (s aapl) devices.I long suspected these problems had much to do with Facebook’s use of various Web technologies, since much of the mobile platform was built with web standards and technologies such as HTML5, surrounded by a native wrapper for Android or i OS. Now I am, thanks to Dirk de Kok’s detailed post at Mobtest, which tests mobile applications.The gist of the problem, at least for i OS (and likely for Android as well, at least partially) is two-fold.One problem concerns HTML use with UIWeb Views but without support for Nitro, which is Apple’s Java Script engine.The second happens because the app makes different data calls for similar, but out-of-sync information.
Here’s a pair of excerpts to explain: “For a starter, caching of unchanged content cannot be controlled by the developer.
The FB app downloads the whole timeline HTML every time, and it is up to the UIWeb View to determine whether it needs to download images, stylesheets etc again….
This is tricky stuff, slow and not really thread safe.” “For notifications, messages and friend requests regular REST calls are done, returning XML data.
First check is to see what number of new notifications are there, then the actual content is retrieved in a separate call.
As far as I can tell, the Facebook service calls return inconsistent information.