Goal: To create a public art museum website that allows users to purchase tickets, view events, schedule visits, and view the expected number of people visiting per day.

Target Audience: 18-60 year olds and/or working adults, college students, or users who like to peruse art

Key Challenges: Handling all stages of the process on my own

Constraints: Usability study is limited to the social circle, only one main viewpoint for the entire project

The required research for this stage was mostly the same as the previous portfolio project.

In summary, I used qualitative research as grounds to create user personas, a user journey map, and a competitive audit.

The key questions that guided me during this stage were: 

• Lack of time

• Subject Interest

• Other visitors

• Cultural Indifference

The same personas as before were also used.

I then developed a goal statement and problem statement.

Goal Statement: The public art museum app will allow users to schedule visits, view day-to-day events, and see estimated visitors per day, which will affect demographics of all ages who have interest in art by allowing them to be able to pick the most suitable day to visit the museum without any worries.

A competitive audit was made to understand how other companies structured their websites.

During the wireframe process, I first drew paper wireframes to allow for quick idea generations.

My primary goal was to include ways to show the site's personality and values with an engaging design.

Then, after finalizing my wireframes, I converted them into a digital layout.

I designed both the desktop and mobile versions of the website. My concern here was to make sure that the website's content was easy to understand regardless of screen size. I also put more focus on the schedule page, which would be one of the core parts of the user flow.

Unfortunately, due to some limitations, not all webpages could be created. However, I ensured that the core of the website could still be shown.

The digital wireframes were then made into low-fidelity prototypes to test interactivity.

Nodes were added to each page to ensure that, during testing, users were able to easily navigate to the needed sections.

After completing the prototype, I did an unmoderated usability study. This study was limited due to my lack of diverse participants willing to take part within the specified time. The participants were three women and one man.

Accessibility

Measures were taken to ensure the design and flow were accessible to all users.

1. The checkout page would be accessible via the Ticket Page or the Schedule page. If accessed through the Schedule page, it would input the selected date for the user. The user also has the choice to either manually type the date or select from the embedded schedule.

2. The site navigation can either be found at the top of the page or at the bottom. This makes it easier for users to access the pages they want on the web.

3. Users can view their tickets upon purchasing. Though not shown, if the user clicks View Ticket, they will have the option to download. The ticket would also be sent to the user's email address upon payment confirmation.

Takeaways

I learned that color is a great way to break up content and make things more readable. Even if your palette is only three colors, you can implement them in various ways to highlight or emphasize information. There is also the importance of language. I found adding friendlier language makes the page more personable and fun to interact with.

This project was a great way to put the things I learned in my previous project (the app version of this concept) to the test.

Overall Feelings

The only regret I have for this project is not adding the rest of the webpages for the site. My primary concern was to demonstrate the user flow, so I forewent the other pages that can be found in the navigation. Adding them all, while completing the website, would take up space in the content I wish to show. Other than that, I am satisfied with the site.