Mobile Development Considerations (Magic xpa 3.x)
When developing a mobile application, it is recommended:
-
To have most of the screens as offline screens with local data.
-
To use sync programs to get the data to the client.
When you do the above, the application will be available to the end user even if the network or your server are not available.
If the entire application needs to work while being connected to the server (for example, a banking application that does not store any information on the client), the first screen should be an offline screen.
This is important to provide a better user experience as follows:
-
If the network or your server are not available, at least the first screen will be seen.
-
If the user kept the application open and the context was closed on the server, the application will return to the first screen (and not be closed).
Also note that when uploading the application to the Apple store, Apple will reject the application if it will not load (such as if the network is unavailable).
It is also recommended to deprecate the connection error messages using the ClientSessionSet('EnableCommunicationDialogs','FALSE'LOG) function and show your own messages in the Unavailable Server internal event.
Note: For a list of differences between the various platforms, see the Magic xpa Platform Comparison chart.
