View
Alok Singh / UX
Open · Q3 2026
CASE / 01 2025 · Self-initiated exploration

Altios: design and code, one surface.

A self-initiated 2025 concept for a unified canvas where visual design, component logic and AI assistance share the same workspace. Today most teams play telephone across Figma, Storybook and Jira. Altios proposes a single surface so a team's intent reaches the build without three rounds of translation.

RoleConcept lead, end to end
Year2025
TypeSelf-initiated exploration
OutputVision, IxD model, system sketches
Altios concept canvas, unified design and code surface
§ 01 · Context

The translation tax.

Today's product teams move ideas across at least three tools. The designer's intent enters Figma. Engineering reads it through Storybook. Product writes it down again in Jira. By the time the work ships, the original idea has been described four times by four different vocabularies.

Most of what we now call collaboration is the cost of paying that translation tax. Altios began as an attempt to imagine the work without it.

Altios concept screen showing the unified workspace
Fig. 01 · Workspace concept, design and code as adjacent views
§ 02 · Approach

One canvas, two languages.

Altios proposes a workspace where visual design and code are not adjacent panels but two views of the same artifact. Hovering on a frame shows the rendered surface. Pressing a key reveals its component logic. Dragging in either view edits the other.

Contextual tools morph based on what you are touching, so the chrome is never in the way of the work.

Altios visual flow navigation
Altios contextual tooling
§ 03 · Solution

Components that know themselves.

In Altios a component is not a static record in a spec sheet. It carries its own behaviour, its own data shape, its own accessibility contract. The same node renders in design, runs in production and explains itself to a teammate without three different definitions.

AI lives inside the canvas as an embedded collaborator rather than a chat sidebar. It can complete flows, suggest variants, or refactor a node tree without ever leaving the visual surface.

Altios component intelligence
Altios AI integration

The gap between intent and implementation is where most products quietly lose their nerve.

Altios design system thinking
Fig. 02 · System view, components carrying their own contracts
§ 04 · Outcome

What this exploration is for.

Altios is concept work. It is unlikely to ship in the form sketched here. The point is to take seriously the assumption that design tools and engineering tools are necessarily separate disciplines, and to ask what a single tool would have to look like if we did not.

It is a north star, not a product spec.

Next case ↓ Wenplus: investing, made legible.