Design KDE apps that feel at home.

The KDE and Kirigami design guidance in one place, in plain language, with a real screenshot next to every rule and component.

Start readingBrowse components
A Kirigami notes app with a sidebar, a page header with actions and a list of notesA Kirigami notes app with a sidebar, a page header with actions and a list of notes

Start here

What KDE design is about and how to read this guide.

Foundations

Colour, spacing, type and icons: the rules every screen shares.

Patterns

How to solve the problems every app has: getting around, showing content, asking, and telling.

Components

The building blocks Kirigami gives you, and when to use each.

PagesA page is one screen of your app. Kirigami gives it a title bar, room for actions, and navigation that adapts from desktop to phone.
Actions and toolbarsAn action describes something the user can do, once. Kirigami turns it into a toolbar button, a menu item or a context-menu entry as space allows.
List itemsThe rows of a list. Qt and Kirigami provide ready-made ones for the common cases, so rows look and behave the same in every app.
CardsA card groups a picture, some text and a few actions about one thing into a single framed block.
Form layoutFormLayout lines up labels and controls in two tidy columns, and rearranges them by itself when the window gets narrow.
Text fieldsKirigami adds three specialised text fields to the standard one, for searching, for passwords, and for fields with a built-in button.
ChipsSmall rounded labels for the tags, filters or properties attached to something.
Navigation tab barA row of labelled icons for switching between the few main places of an app. On a phone it sits at the bottom, within reach of a thumb.
DrawersPanels attached to an edge of the window. The global drawer is the app’s sidebar; other drawers slide in when asked.
Inline messagesA coloured banner inside the page that tells the user something important and, ideally, offers a way to deal with it.
Placeholder messagesWhat to show where content would be when there is none yet, so an empty page explains itself instead of looking broken.
Progress and loadingThree ways to show that the app is busy, depending on whether you know how long it will take and how much of the screen is waiting.
DialogsA dialog interrupts the user to get a decision. Use one only when the app cannot continue without an answer.
Overlay sheetsA panel that floats over the page to show extra content for reading. It scrolls if the content is long and closes with a click outside.

Tutorial: a to-do app

Build a small, complete Kirigami app in seven steps, with the code and a screenshot at each one.