Simulating Networking

Mobile applications can be divided into stand-alone and client-server applications. However, the difference is not always clear. Stand-alone applications may offer the possibility to refresh or update information from a server, and client-server applications may store recent information on the device, thus enabling use of the application without server connection.

Additionally, connection to a server can be established through a variety of services, such as Bluetooth, WLAN, or the mobile network. If possible, the application should use the most sensible connection method, such as a WLAN for internet connection, when available.

Hide the complexity of network connectivity in your applications. Short network coverage problems should not cause loss of users' work or stop them from working. Connection status should be displayed clearly. Synchronization should be automatic but under user control.

When users move around with their mobile device, the device connects to available cells with sufficient signal strength. You can change the network settings to test how the application handles roaming from one cell or network to another.

You can use Qt Simulator to test applications that use the Qt Bearer Management API to manage the connectivity state to the network. Change the Network mode properties, such as Status and Signal strength in the Network section.

You can also load the sysinfonetwork.qs example script to test how your application behaves when the device moves between cells with varying signal strength in a GSM network. For more information on loading scripts, see Scripting.