Low Fidelity UI Prototype

The posts bellow are my low fidelity prototypes for the website and mobile application.

Figure 1: Page 1 of how to purchase a ticket.
Figure 2: Page 2 of how to purchase a ticket.
Figure 3: Page 3 of how to purchase a ticket.
Figure 4: Page 4 of how to purchase a ticket.
Figure 5: Page 1 of how to access the options menu.
Figure 6: Page 2 of how to access the options menu.

The images above demonstrate how the website would work if the user would access it. Figures 1-4 show how purchasing a ticket would look like where the user would access pages for selecting what festival they would like to attend, how long they would like to attend it for and the personal details page to complete the transaction. Figures 5-6 show what it would look like to access the options menu, within the options menu users could change the zoom of the page, the language of the words within the website and the colour of the website in case users may have a visual impairment.

One of the constraints of how to guide a stakeholder to correct choices would be seen in Figure 3 where the user has to select one of the to options to proceed as the “Buy Tickets” button is unable to be clicked. Another constraint is shown on Figure 4 where the mandatory section has to be completed to then proceed to the next page of the transaction.

Figure 7: Page 1 of how to access the tickets page.
Figure 8: Page 2 of how to access the tickets page.

The images above (Figures 7 and 8) demonstrate how it would look like to access the tickets purchased within the mobile application in which the user must save to then gain access to the festival once it opens.

Figure 9: The image above shows the HTA for my festivals website.

Figure 9 demonstrates the HTA (Hierarchical Task Analysis) of my festivals website on how to access the festival, all the way from how to purchase the tickets to how to gain a card.