Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Analysis: Mobility Apps: Page 3 of 12

A number of other technology drivers are accelerating deployment of mobile applications, by which we mean apps that involve communication between a mobile device, including phones, wireless PDAs and laptops, and enterprise servers. Some mobile applications also can operate in a standalone, disconnected fashion, while others, such as most wireless e-mail systems, can operate as islands at times, then synchronize with your or third-party servers when network connections are available. There are also always-connected models of operation, especially for browser-based applications. Of these approaches, the "sometimes" or "usually" connected model is the most common--and generally the most effective. We run down market forces in "What's Driving Adoption," below.

Given today's 3G networks, powerful laptops and handheld devices (which we refer to as smartphones even for PDA form factors), we already have all the computing and networking power needed to extend data to mobile workers. What's been missing has been a wide selection of off-the-shelf software applications. Previously, enterprises may have selected hardware to solve a specific business problem. Now, companies frequently purchase smartphones to address one set of problems, then look to migrate additional applications to the platform, much as in the desktop environment.

However, running applications designed for always-connected, high-speed networks with low latency over wireless links too often results in sluggish and/or unreliable behavior. It's common to experience temporary loss of connectivity, reconnections with different IP addresses and inconsistent throughput levels due to high network load or poor signal conditions, where the wireless link may have to retransmit a large percentage of packets.

Also, older networks, such as GPRS, simply moved packets too slowly (tens of kilobits per second) with too much latency (hundreds of milliseconds). Dealing with the foibles of 2G wireless often meant employing wireless middleware, which could involve rewriting the application or developing custom apps using programming interfaces specific to the middleware. The result: Expensive and cumbersome application deployment, often justifiable only for focused vertical market applications, such as dispatch or field service.

Three things have changed to improve this situation dramatically. First, wireless networks have become much faster; applications that ran poorly on 2G often perform well on 3G networks. That SQL database application might refresh a screen in 5 seconds instead of 30.