Symantec Mobility: Suite custom app configuration requirements for Android apps
Last Updated September 17, 2014
Unlike iOS, Android doesn't have device management. So there's no built-in way for a server to send a configuration to an app. To use the custom app configuration feature in Mobility Suite, app developers must create or modify their app code to look for the app config data.
Android has a SharedPreference configuration object similar to Apple's NSUserDefaults. The counterpart to Apples key com.apple.configuration.managed is the name of the shared preference. The Mobility Manager-supported app management object name is standardUserDefaults. The object is retrieved with code like this:
If multiple key/value pairs are changed at the same time, they are committed to the SharedPreferences object in a single operation and then onSharedPreferenceChanged() is called once for each changed key/value. If a key/value pair is removed from the SharedPreferences object, onSharedPreferenceChanged() is called with the removed key. So if the key passed to onSharedPreferenceChanged() doesn't exist in the prefs object, then that key/value was removed.
Just like for Apple, it is assumed that the app is expecting key/value pairs to be from the app's documented configuration options.
Imported Document ID: TECH218351
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe