Responsibility for preserving data integrity between handheld device and network data store doesn't rest exclusively on the device management platform you choose; equal responsibility rests with the enterprise developers building the applications in the first place.
There are caveats, however: since most mobile devices have small pen-driven screens and only a few have even smaller keyboards, usability is a major concern. This not only impacts application design -- for example, requiring uncluttered and intuitive application screens that validate entered data and don't rely extensively on keyboard input -- but also affects mobile device management strategies.
"Web services has come a long way in helping the integration of these devices," says Eric Sibly, solutions architect with solutions development giant Avanade. "A reduction in filling out manual forms means companies can get their processes moving a lot quicker, and built-in reference data can improve the timeliness and quality of information they're getting. However, in applications where you need to do real-time updates, you've got to look at the type of connectivity and make sure you know what happens if the wireless link fails."
Avanade had to address this exact problem during a recent project with Queensland Rail, which recently worked with Avanade to build a shipment scheduling system that used PDAs and the CDMA mobile network to let train drivers bring detailed information on shipments along with them. With uncertain wireless coverage in regional areas, the application had to be designed with enough data permanence to ensure that they remained usable even in black spots. Collected data is stored on the devices until it can be synchronised back to the home server once the CDMA signal is picked up again.
I just watched a webcast on managing Windows Mobile at http://www.microsoft.com/events/series/msecmobility.aspx. I would guess that mobile phone use will grow quickly in the next decade.