How can we help Siri QA testers spend their day testing instead of copying data between tools? The macOS app they used every day had grown one feature at a time, and it was time for a redesign.

Contribution. Product Designer, UX & UI, Redesign lead.

Tools. Sketch, Xcode, SwiftUI, Claude Code.

Note. Under NDA. All visuals are illustrative schematics with sample data, not the shipped interface.

Schematic of the redesigned testing window

Schematic of the redesigned testing window: test cases on the left, the selected case and its form on the right

I led the redesign of a native macOS app that Siri QA testers use to run test requests, record findings, and report defects. Since testers already used the tool every day, I started with field studies and interviews to see where testers lost time.

When a test failed, testers filed a ticket in a separate tracker. A failed test already holds most of what a ticket needs: the test case, request, build, device, language, region, steps, and recordings. Testers were typing all of it a second time.

In field studies, I watched triagers copy details from previous tickets, or from the app into the ticket, and sometimes miss things. Leaving the test run also broke the tester's place in the test pass.

Schematic of the Create Ticket sheet

Create Ticket fills about 20 fields from the test run and leaves 4 for the tester to decide

I added a Create Ticket button to the footer of every test case, next to Submit. It opens a ticket sheet, and the tester reviews and files it. The ticket links back to the run, so neither side loses the connection.

The sheet fills in every field the run knows and attaches the recordings, logs, and screenshots from the session.

qa-tester-flow

The tester’s flow, from test case to ticket

When a test fails, the ticket opens inside the run, already filled from the evidence. The ticket and the test result submit together, and the tester moves on to the next case.

The ticket tracker is a free-form text box every team uses. The new form shows testers what each ticket needs, so triagers accept it the first time.

Every new feature had added another menu item or keyboard shortcut. Experienced testers memorized them; new users searched through menus by hand and often didn't know a feature existed.

Schematic of the command bar

The command bar finds actions by name or intent and shows each action's shortcut

I designed a command bar that opens from anywhere with ⌘K. Testers type a few letters of what they want, and the bar finds the action, even by an alias or a verb. Each result shows the action's shortcut, so testers pick them up as they work.

An empty bar shows each person's recent and frequent actions. I added a registration pattern so every new feature appears in the bar from day one.

User tests and a survey both showed testers wanted more keyboard navigation, so the command bar launched with hotkeys. Testers already use ⌘-Space to get around macOS, so the pattern was familiar. Reorganizing the menus would have broken the muscle memory of experienced testers who knew where everything lived.

qa-error-handling

Three of the error states: missing fields, tracker unavailable, and a known issue

Every error keeps the tester’s work and gives them a next step, from highlighting a missing field to saving a draft when the tracker is down.

The same button looked different from screen to screen, and every new screen started from zero. To make the redesign hold, I built a component library in both design and code.

Token naming rule

One naming rule for every color token

I audited every existing control and grouped them by the job they do, which exposed duplicates their names had hidden. Color tokens follow one naming rule, color-{element}-{priority}-{state}, which kept the set small and ended naming debates. Each component covers every state, light and dark appearances, and guidance on when to use it.

AI speeds up both ends. I use it to turn Figma designs into working SwiftUI code that developers integrate into the app, and to run the component audits that keep the design and code libraries in sync.

The biggest constraint was that the tool was live. Testers couldn't stop testing while we rebuilt it, so screens moved to the new components in small, reviewable steps instead of one large change.

The design and coded libraries also had to stay in sync. I audited them against each other after every major update, so the library developers built with matched the designs. I checked keyboard navigation, VoiceOver labels, and contrast throughout.

Filing a ticket now takes 3 clicks, and the tool handles about 20 fields and all session files for the tester. Before the redesign, filing a ticket took 2 to 5 minutes on average. Triagers now report that far fewer tickets come back for more information when testers file them through the tool.

The team has migrated all tokens, and about 90% of components now use the updated library. Every new feature uses the new components; the rest wait on legacy code cleanup.

Say hello!

Let's Connect