Expertise
Front ends that belong to a real system
We build front ends as part of the product rather than as a separate workstream. Operator consoles, customer applications, and Databricks Apps that run in the workspace. Design engineers and software engineers sit on one team, so the interface is decided while the data and the permissions can still change. Smaller starts work too: a design system, a component library, or one console we build and hand over. Several of our longest engagements began that way.
A front end is only interesting if something trustworthy sits behind it.
What we build
- Customer-facing applications and the admin surfaces that run them
- Design systems carried from one product to the next
- Databricks Apps when the interface belongs next to the data
- Front-end work staffed with the people who own the API behind it
Accelerators doing the work.
When the interface is a Databricks App, Runway is how it ships. When the product needs an auditable console, Platform is underneath.
How this is delivered
Platform & SaaS development
Full product delivery: multi-tenant architecture, operator consoles and the data layer under them. Shipped as Databricks Apps when the product belongs next to the lakehouse.
FAQ
Questions we get asked
Do you take front-end-only contracts?
Yes, and it is often how an engagement starts: a design system, a component library, or a single operator console. Where we add the most is when the system behind it is ours too, and that is usually the conversation a few months in. Platform delivery is at /services/platform. For a pure marketing site a specialist studio will serve you better than we would.
What stacks do you use?
Whatever the product already runs, if we are extending it. On new work it is usually a modern TypeScript application. On Databricks it is often a Databricks App, delivered through Fabric Runway at /accelerators/fabric-runway.
Is this the same as experience design?
They sit together. /expertise/experience-design is the design case. This page is the engineering of the interface. Both route into the same team.
Tell us what is stuck.
A technical conversation about the interface and the system behind it.