Personalization Key Example

This example demonstrates how the personalization key value storage settings affect mobile application behavior.

Personalization values are scoped to a named user. For example, the mobile application developer creates a weather application that includes a personalization key named "zipcode". In this example:

John sets the zipcode personalization value to "94568" and automatically gets the weather for Dublin, CA. If the weather application is installed on both John's iPhone and laptop and storage is set to "server", the value is shared across all his applications.
If John sets the zipcode to 94301 from his iPhone, the next time he views the weather application from his laptop, it shows the weather for Palo Alto instead of Dublin.
If storage is set to "client", each instance of the application maintains its own setting for the value. So if John changes the zipcode on his iPhone to 94301, the laptop still shows Dublin weather.
If storage is set to "transient", the value must be reset each time the application runs - it is not persistently stored anywhere.
If the weather application used "GPSLocation" personalization key instead of zipcode, the weather application could retrieve current location using iOS native O/S calls to set the transient GPSLocation personalization value before synchronizing the weather MBO.