Five Lessons on Interface Design
January 26, 2024 · Arthur Gray · 6 min read
The most useful ideas came from people who use the product every day. Thanks to everyone who sent comments and suggestions. We rely on open formats so the data can be exported at any time. The hardest part was not the code but agreeing on how the team should work.
If something does not work as described, let us know and we will fix the text. Configuration details are covered in the following sections. Nothing here is a solo effort: a small team works on the project.
We started with a small prototype and slowly turned it into a working product. The design system grew from a couple of pages of notes into a full reference. We rely on open formats so the data can be exported at any time. Every change is rolled out to a small group of users first. Configuration details are covered in the following sections.
Documentation
We started with a small prototype and slowly turned it into a working product. These pages are updated whenever a new version ships. We kept the old interface available until everyone had moved over. It turned out that half of the time went into agreeing on small details. Every week we pick one problem, dig into it and write down what we learned. The project moves in small steps, and that is its main strength.
const client = new Client({ baseUrl: "https://api.linden.sweet-lab.shop" });
const items = await client.list({ limit: 20 });
Planning
We try to write code that will still be easy to read a year from now. Thanks to everyone who sent comments and suggestions. A good layout starts with the text, not with the pictures. We keep a changelog so it is always clear what changed and when.
A good layout starts with the text, not with the pictures. People rarely read manuals, so hints have to be short and specific. We keep a changelog so it is always clear what changed and when.
- Documentation
- Visual Style
- Testing
- Interface Design