Product update2 min read

Designing a more cohesive Avara

A pass over every screen in the product — one visual language, calmer surfaces, clearer states — so the interface gets out of the way of the decisions it supports.

StatusIn development

After we simplified Avara around three questions, the product made more sense — but it did not yet look like one product. Screens built at different times had drifted apart: different surfaces, different type sizes, different ways of saying the same thing. So we went through every screen.

One visual language

We defined a single set of design tokens for the product: layered navy surfaces rather than pure black, three border strengths, four levels of text, one accent, and colours that carry meaning only — success, warning and danger. A shared type scale and spacing grid replaced hundreds of one-off values. In the product's stylesheets, literal font sizes went from 157 to 2.

We also removed things. The product no longer has a starfield behind it, glowing buttons or frosted-glass panels. They looked good in a screenshot and made dense information harder to read.

Clearer states

Much of the work was about making state legible:

  • A work item's lifecycle is now a compact track. Only the stage that is happening now explains itself, and a future stage never looks reached.
  • Verification reads as an evidence report: the result, a tally, and for each check what was expected and what Avara observed.
  • Raw machine timestamps are gone from the interface.
  • The integrations page no longer shows server setting names to customers, and each connection says whether it is connected, syncing, failing or needs reconnecting.

Deliberate decisions

Approving or declining work now takes a confirmation that names the item and says what approving means. It is one extra click, placed beside the button rather than in a modal, for the decisions that set work in motion.

Accessibility and words

Every interactive element has a visible focus ring, body and supporting text meet WCAG AA contrast on every surface they sit on (the lowest pair we measured is 5.4:1), and motion is reduced when your system asks for it. We also settled the words: the same stage names everywhere, "coding agent" instead of "developer", and one spelling throughout.

Where this stands

We reviewed every screen at five widths, from a large desktop down to a phone. The redesigned interface is deployed with our web application, but it sits behind sign-in and Avara is in closed beta, so it has not yet been in front of beta customers. We describe it as in development until it has.