All posts

Translating Swiss design to software

An experiment in bringing Swiss graphic design into modern software interfaces.

5 min read

I've always liked Swiss design, particularly its use of typography, grids and whitespace. I've used the style in static projects like posters, and wanted to see what it would look like applied to a software interface.

I built an email campaign tool as a test case, exploring how the same visual language could work with responsive layouts, tables and changing content. The result combines a typographic grid, modular spacing and a stripped-back interface with fewer borders and panels.

Typography and spacing

The interface uses a 16px base unit. Margins and gutters follow that unit, while table rows take up two units. Text is aligned to a 4px baseline grid using CSS text-box trimming and calculated offsets.

Trim the text to its letters, then push it down to the next grid line.
.rx {
  text-box: trim-both cap alphabetic;
  padding-top: calc(round(up, 1cap, 4px) - 1cap);
}

Text-box trimming isn't supported in every browser yet. Without it, the text sits a few pixels off the baseline grid, but the layout itself holds.

This gives the interface a consistent rhythm, with typography, spacing and component dimensions working together rather than feeling independently styled.

Phase 172h interval
1
Welcome email
48%
2
Getting started guide
41%
3
Tips & tricks
37%
13px type on a 16px line. Margins and gutters are one line, rows are two, and every baseline sits on the 4px grid.

A responsive grid

The layout uses 24, 12, 8 or 4 columns, depending on the available width. The navigation follows the window's grid, while the main content sits in a separate container with its own columns and maximum widths.

Tables adapt to narrower screens by dropping lower-priority columns first. A designated column expands to fill the remaining space, keeping the table usable without needing a separate layout for every breakpoint.

0px · 4 columns

Drag the window's edge. Blue is the window's grid, red the container's. The navigation folds away below eight columns and the table drops its least important columns first. From 1744px the window takes 24 columns.

Working with real content

Unlike a poster, an interface has to accommodate content of varying lengths. Text can wrap across additional lines, and the layout grows with it while retaining consistent spacing.

Description

Build the sequence by adding emails and grouping them into phases.

Phase 1 · 72h interval
1Welcome email
2Getting started guide
3Tips & tricks
Description

Build the sequence by adding emails and grouping them into phases. Emails in a phase go out in order at the set interval, and each phase waits for the one before it to finish. Build the sequence by adding emails and grouping them into phases. Emails in a phase go out in order at the set interval, and each phase waits for the one before it to finish.

Phase 1 · 72h interval
1Welcome email
2Getting started guide
3Tips & tricks
The same block with a short and a long description. The text takes whole lines, so the rows under it stay on the baselines.

Section labels sit in a separate column beside their content, moving above it on narrow screens. For larger datasets, group labels remain visible while scrolling, and long lists can be expanded in batches.

Email campaign tool
The email tool with hundreds of emails in it. Scroll through it, or open it larger.

Fewer borders

I also experimented with removing the panels, cards and borders commonly used to separate interface elements. Instead, spacing and alignment do most of the work.

The current version, with a few borders brought back.

The result is quieter and closer to the graphic design that inspired it. But removing every boundary also made some elements harder to recognise. Buttons and inputs need clear affordances, and dense tables benefit from subtle dividers. I brought some of those details back where they helped.

Was it worth it?

I'm happy with the experiment as an exploration of Swiss design in software. The grid gives the interface a consistent structure, and the reduced use of boxes creates a different feel from a conventional dashboard.

I'm not convinced the aesthetic suits every product, and that's fine. The point was to see how the style translated to an interactive interface, not to establish a new design methodology.

– Joan