Determines the URL where the REST Web Services of the mobile application may be found.
Generators: Android, Apple
The Service URL should have a structure like this:
<protocol>://<server_domain>[:<port>]/<virtual_directory>
where
- protocol: It can be http or https, depending on your requirements.
- server_domain: The domain of your webapp (it could be an IP address as well).
- port: Optional. Port number where the server is listening.
- virtual_directory: The location of your REST web services.
See Online Native Mobile applications architecture for more information about the architecture and the role of Rest Services in this kind of apps.
There are Native Mobile Client apps where the Server providing the services is defined by the Client. So, the application does not actually have the server URL defined at design time. This is a common scenario for many applications where the Server-side is a product in itself.
Basically, instead of defining, at design time, where my User Interface will consume services, it is defined in a client application setting. In this case, the Services URL property should be left empty so that upon accessing the application, the end-user will be required to enter a Services URL value.
However, you should consider setting a default value for the device's services URL property because it is a requirement of Apple's approval process.