Applications
Applications are built for a target MobileFirst Server. They have a server-side configuration on the target server. You must register your applications on the MobileFirst Server before you can configure them.
- An app ID
- A version number
- A target deployment platform
- Android
- For Android apps, the identifier is the application package name.
- iOS
- For iOS apps, the identifier is the application bundle ID.
- Windows
- For Windows apps, the identifier is application assembly name.
- Web
- For web apps, the identifier is a unique ID that is assigned by the developer.
- An iOS app with a bundle ID of com.mydomain.mfp
- An Android app with a package name of com.mydomain.mfp
- A Windows 10 Universal Windows Platform app with an assembly name of com.mydomain.mfp
- A web app with an assigned ID of com.mydomain.mfp.
- An iOS app that you develop with Xcode and native code
- An iOS app that you develop with Cordova cross-platform development technologies
Application configuration
An application is configured on both the client side and the server side. For native and Cordova iOS, Android, and Windows applications, the client configuration is stored in a client properties file (mfpclient.plist for iOS, mfpclient.properties for Android, or mfpclient.resw for Windows). For web applications, the configuration properties are passed as parameters to the SDK initialization method (see Initializing the MobileFirst SDK). The client configuration properties include the application ID and information such as the URL of the MobileFirst Server runtime and security keys that are required to access to the server. The server configuration for the app includes information like app management status, web resources for Direct Update,configured security scopes, and log configuration.
The client configuration must be defined before you build the application. The client-app configuration properties must match the properties that are defined for this app in the MobileFirst Server runtime. For example, security keys in the client configuration must match the keys on the server. For non-web apps, you can change the client configuration with the MobileFirst Platform CLI (mfpdev command).
The server configuration for an app is tied to the combination of app ID, version number, and target platform. The version number is not applicable to web apps. You must register your app to a MobileFirst Server runtime before you can add server-side configurations for the app.
On a production server, the app version typically corresponds to the version of the application published to an app store. Some server configuration elements like the configuration for app authenticity, are unique to the app published to the store.