| Wireless environments introduce some characteristics that are not common in wired ones. These characteristics set the requirements for the Client implementations in mobile devices. In addition, these characteristics also result in real benefits, explaining why SyncML should be implemented in mobile and wireless devices. The SyncML Client software architectures can vary widely between wireless devices. Such architectures are dependent on the device platforms at which the software is targeted. Nevertheless, there are some common characteristics, which have been discussed in this chapter. In addition, there are common crucial requirements, which need to be considered. Excellent performance and usability are important factors that improve end-user satisfaction. Having different application types enabled by the Client software can definitely help differentiate mobile devices and their Client implementations. Interoperability should not be forgotten when aiming at such differentiation. Interoperability is not only an issue in designing the SyncML protocol, but must also be taken into account in designing the applications. The architecture of Client software in a mobile device does not need to be complex. Actually, to fulfill the requirements related to footprint and performance, it must not be complex. A simple architecture implies that SyncML can be implemented easily for mobile devices. This further implies that more and more mobile and wireless devices will support SyncML, and the end-users can substantially benefit from the power of universal data synchronization. | 
