This design example describes a scenario for an end user's first-time purchase. The content is not protected with built-in DRM, and the user is not yet signed in to Nokia Store.
The user is travelling to Helsinki, and wants to purchase the Helsinki tour guide for the trip in their the Guided application. The situation is the following:
The user is purchasing the first guide for the application.
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.
Screen 1: To see the application's catalog for purchasing the guide, the user presses the Buy more city guides button. |
Screen 2: Because the application does not yet know if the user has previously purchased some items that could now be restored, it displays a link to the user to check if any purchased items are missing. The user decides to press the Helsinki guide to read information about it. |
Screen 3: The user chooses to purchase the guide. |
Screen 4: Because the user is not signed in, Nokia Store prompts the user to enter the password. |
Screen 5: When prompted by Nokia Store, the user confirms the purchase. |
Screen 6: Nokia Store is processing the purchase. |
Screen 7: When the purchase is complete, Nokia Store confirms that the payment was successful. The application starts the download in the background. |
Screen 8: The guide is being downloaded. |
Screen 9: When the download is complete, the newly purchased guide is moved from the purchase catalog to the user's library in a coherent transition, showing the user where it can be accessed. |