HTML5 pace set by carrier dog days, not developer dog years

30 November 2013 by Steve Blum
, , , , , , ,

Puppies for a while longer.

The Firefox OS is built to run thin client HTML5 applications, which depend heavily on network connections to store data and offload processing. So far, the available applications are a promising mixed bag, at least judging by performance on the first readily available Firefox phone, the ZTE Open.

Both the Facebook and, particularly, the Twitter apps are consumer-ready, but most of the other available apps are little more than browser bookmarks that take you to a website. The included email and calendar apps work well with both Google and Apple services, and deliver a smooth user experience. The address book, though, needs a lot of help. It’ll only sync with Google contacts and it’s not well integrated with the phone – dialling directly from a contact is a clunky chore and it’s difficult to, for example, reply quickly to a phone call with a text message.

Mozilla is just one of the companies betting that HTML5 will fullfil its promise of “write once, run everywhere” apps. Tizen and Sailfish are also counting on a spontaneous wellspring of developer support as the language matures, although both of these Nokia MeeGo-descended OSes are also hoping to grow proprietary ecosystems. Jolla released its SDK for the Sailfish OS earlier this week, with a heavy emphasis on its support for Android applications.

The challenge for HTML5 developers is to find a proper balance of on-board functions and network services. Achieving acceptable performance depends on the speed of mobile broadband connections, so the speed of development will be governed, to a large degree, by the upgrade plans of carriers. With other alternative OSes available, developers might not want to wait.