Member mobile app

About

Context

Maestro is a ticketing and patron system for performing arts organizations, built on Tessitura. This is the member side: the app a subscriber opens between buying a ticket and walking into the hall.

Audience

A subscriber, not a buyer. They renew every season, hold the same seats, and come to six or more performances a year. They were converted years ago, by the orchestra rather than by an app, and nothing on this surface needs to convert them again.

That one fact deletes most of a ticketing app. No account creation, no discovery funnel, no upsell, no persuasion. What remains is narrow and specific: what do I hold, what happens next, and what am I owed. The app should answer all three before they think to ask.

They are also older than the median app user, often attending with a spouse or a household member, and reading in a low-lit lobby minutes before a downbeat. That sets the type size, the contrast floor, and the decision to put seat and section in monospace so they can be read aloud when a scanner fails.

The second audience is the team deciding what to build. The navigation map is drawn for them rather than for the subscriber, which is why unbuilt work sits on it, labeled, instead of quietly missing.

Output

Ten screens. Four destinations: Home, Events, Tickets and Profile. A navigation map of the whole surface, where thirty four of fifty three places are built and the other nineteen are drawn and marked as not built. Every node with a screen behind it opens that screen.

Alongside the app, an identity system and a design system: type, color, spacing, motion, components, voice, and the token layer under all of it.

Two things stay unfinished and say so on the page. The typefaces are trial and desktop licenses, so two strings fall back mid word. The member pass shows no scannable code, because there is no credential system to draw one from.

Counts here are read off the register and the map, not kept by hand. If they drift, the source moved.