Museum App — Research Case Study

An inclusive app for a public art museum so visitors can find exhibitions, see clear pricing, and reserve a timeslot quickly, regardless of language or accessibility needs.

Problem Statement

Many visitors face language barriers and accessibility hurdles when trying to discover and book museum events. Current sites are often English first, inconsistent, and not friendly to screen readers. This leads to confusion, drop-offs, and missed visits.

Product Goal

Help people find an exhibition, understand the price, and confirm a booking in three simple steps. Reduce language friction, surface the right events fast, and support screen readers from start to finish.

  • Reach a relevant event in under thirty seconds
  • At least thirty-five percent booking conversion
  • Ninety percent task success for screen reader users
  • Twenty-five percent return rate within sixty days

Personas

Primary audiences that shaped early decisions

Persona showing a busy visitor who relies on a screen reader and values quick booking
Persona A — time-pressed visitor who needs a fast, accessible flow.
Persona showing a newcomer who benefits from multilingual options and clear pricing
Persona B — newcomer who benefits from multilingual options and clear pricing.

Early Designs

Paper explorations and low-fidelity wireframes

Paper wireframes of the home screen, calendar, and the time and tickets flow
Rapid sketches for navigation, the calendar, and a three-step booking flow. I noted labels, focus order, and clear errors to support accessibility.
Digital wireframes of home, event details, tickets, and checkout
Responsive wireframes with readable event cards, a visible language toggle, and student pricing shown early in the journey.

Competitive Audit

Scope: ROM, the Louvre, MoMA, and Google Arts and Culture — reviewed September 2025

Snapshot of a competitive audit table with notes on calendars, language controls, and checkout
I looked at how leading products handle discovery, multilingual support, and checkout. I kept what worked—event-first navigation and strong visuals—and improved gaps: a persistent language toggle, a three-step checkout, and student pricing shown on cards.
View the full tableScreenshots are for educational critique. Trademarks belong to their owners.

What I will keep

  • Event-first navigation with a clear calendar and filters
  • Language control visible in the header
  • High-contrast components that are friendly to screen readers

What I will improve

  • Student pricing shown on cards and on details
  • Three-step checkout with Apple Pay and Google Pay
  • Personalized suggestions such as “Because you liked …”