This design example describes a scenario where an end user's purchase attempt changes into a restoration of the product. The content is not protected with built-in DRM, and the user is signed in to Nokia Store.
The user has earlier purchased city guides for a guided application on their old device, and now wants to restore the same guides on their new device. The situation is the following:
The user has previously purchased content on a different device, and still has the right to re-download that content.
The user is already signed in to Nokia Store. This means that when launched, the application can silently first check the user's identity from Nokia Store, and then check the availability of restorable items from the back end server. No password prompt is needed, and the application can display the restorable items right away, if any are available.
The user requests to restore the previously purchased content, and downloads it.
Screen 1: To see the application's catalog for purchasing guides, the user presses the Buy more city guides button. |
Screen 2: Because the application already knows the items that the user is allowed to restore, it is able to display options to restore them, in addition to all the purchasable new items. Instead of purchasing new items, the user chooses to restore all the restorable items. |
Screen 3: Because the user is signed in, Nokia Store does not ask for a password. The items are being restored from the back end server. |
Screen 4: When the restoring is complete, the restored items are moved from the purchase catalog to the user's library in a coherent transition, showing the user where they can be accessed. |