Prototype Iteration 2

Second Stage

The second stage is developed based on the user testing conducted from the previous design prototype. In this stage we add a tutorial or help page where user can learn how to use the product.

Installing Puzzle Pay for the First Time

Puzzle Pay Chrome Extension Web Page

User can install the Puzzle Pay extension by opening the Puzzle Pay's Chrome Web Store Page. The page consists of screenshots and short overview of what Puzzle Pay is and why should people use Puzzle Pay. By clicking the "Add to Chrome" button, user can install Puzzle Pay.

Signing Up to Use Puzzle Pay

After Puzzle Pay has been installed, the user will be redirected to a sign-up page. The user needs to be logged in first in order to use Puzzle Pay. From this page, the user can create a new account or Log In to an existing account.

Tutorial Page

The user will access this page directly after they logged in for the first time. This page consists of explanation on how puzzle pay works, and how to use the Puzzle Pay extension. User can also access this page by clicking the help button when they are using the Puzzle Pay extension.

Buying items

User Checkouts on an E-Commerce Website

Puzzle Pay will detect the user if they clicked the checkout button. For example, the above picture shows that the user is currently buying items on Amazon. When the user clicked "Proceed to Checkout", Puzzle Pay will copy the cart items data, and the total amount data.

Puzzle Pay opens

Puzzle Pay will automatically close the previous tab and opens a new Puzzle Pay tab. In order to buy the items, the user needs to go through the puzzle process. Puzzle Pay will show the item cart list, and the total amount that the user needs to pay. Puzzle Pay will ask the user for an Observer email in order to continue the application flow.

Puzzle Page and E-mail to Observer

After the user inputs an Observer email, the page will be redireted to a puzzle page. In order to solve this puzzle, the user needs to contact the observer to obtain the solution. The Observer will receive an e-mail that consists of the user's cart item lists, and the total amount that the User needs to pay. The e-mail will remind the Observer that the User is using Puzzle Pay to control their spending habit. Therefore, the User needs to convince the Observer to give them the solution to the puzzle

Puzzle finished

After the User manages to retrieve the solution from the Observer. The User needs to input the correct solution in order to continue the application flow

User Decides Whether They Still Needs The Item or Not

At this page, the User needs to decide whether they still need the item or not. If the User decides to buy the items, Puzzle Pay will automatically close and the user can proceed to checkout. But, if the User decides to choose No, Puzzle Pay will automatically close with no further actions.

User Testing

We conducted a user testing by using the design files that we created for the current prototype. By creating a flow and redirection upon a click between each pictures of the design, we can emulate a working application. The user testing for this prototype uses the same method and protocol as the previous prototype iteration. By using a think-aloud protocol, and conducting an interview after the testing session is finished, we could gather more important data. The current prototype aims to test the new tutorial feature that was created based on the previous user testing insights. Because our aim is to test the tutorial page, we only give the user a short description of the application before the testing session started. We also wants to know whether the user prefer to input the observer's email everytime they used the application. Based on the user testing that we have conducted, we gained several insights:

• Most of the Users can easily notice the big question mark button and understand what is the use of the button.
• The implementation of the tutorial function helps the user understand how to use the application. Upon installing the extensions, some Users skipped the tutorial page. But when they have trouble while using the application, they opened the tutorial page and read it.
• Some Users suggested to change the puzzle solution to words instead of randomly combined characters.
• Users prefered to enter the observer email everytime they use Puzzle Pay. An issue of privacy was mentioned if the application stores email without the approval of the owner. Based on the insights that we gained, we can see that the implementation of tutorial helps the user when they need help while they are using the application. The tutorial page could be made more attractive as some user tends to skip the tutorial page on the first time.