This design example describes a scenario where an end user is not allowed to restore earlier purchases. The content is not protected with built-in DRM, and the user is not yet signed in to Nokia Store.
The user has earlier purchased city guides for a Guided application on their old device, and now tries to restore the same guides on their new device. The situation is the following:
The user has previously purchased guides on a different device, but no longer has the right to re-download them.
The user is not signed in to Nokia Store. This means that when launched, the application is not able to silently check the user's identity from Nokia Store, and consequently not able to check the user's eligibility for restoration from the back end server. Instead, the application provides a UI option, which the user can select if they want to check if they are entitled to any restorable items.
The user requests to restore the previously purchased guides, but the request is refused. The user will have to make a new purchase to get the guides.
Screen 1: To see the application's catalog for purchasing guides, the user presses the Buy more city guides button. |
Screen 2: The application does not yet know if the user has previously purchased some items that could now be restored. It displays a button to the user to check if any purchased items are missing, and the user presses the button to do the check. |
Screen 3: Because the user is not signed in, Nokia Store prompts the user to enter the password in order to retrieve the data. |
Screen 4: The application now knows who the user is, and also that the user cannot restore any of the previously purchased items due to restoration policies. The application displays options to repurchase the same items. |