About

Maestro is a ticketing and patron system for performing arts organizations, and this is the member side of it: the app a subscriber opens somewhere between buying a ticket and walking into the hall.

We built it as a working prototype rather than a deck, because the questions that actually matter here are about sequence and priority, and those only become arguable once you can tap through them. Eight screens exist. You can move between four destinations, open the member pass, and read the season. Twenty seven of the forty six things the full navigation calls for are built, which is the honest ratio for something meant to settle shape rather than ship.

The person we designed for already pays the organization every season and attends more than once a year, so the app never has to sell them anything. It answers what they hold, what happens next, and what they are owed, and it tries to answer all three before they go looking.

Two decisions are still open, and everything downstream is waiting behind them. The first is what your next action should actually contain, which sounds small until you try to rank a ticket against a benefit against a renewal that closes in a week. The second is what offline really means for the member pass, because a credential that works in the lobby with no signal is a different piece of engineering from one that merely looks like it might.

A few things are unfinished and worth saying out loud. The typefaces are still trial and desktop licenses, so two strings fall back mid word. Only one photograph meets the motion blur direction we set, and the concert hall image is standing in until there is a real shoot. None of that is buried; the pages that document the system say so on the page.

Navigation map, Identity system and Design system are the other three tabs. Every count on this page is read off the map, so it stays true as the build changes.