I would like to welcome readers and contributors.
This project aims to improve the user interface.
Currently, this is being achieved by moving the user interface component out of dom0.
note: that the user interface in question refers only to the interface used by dom0 itself, not the component responsible for displaying applications from other VMs; the latter remains unchanged.
Exiting dom0 is the first step, given its inherent security sensitivity; this ensures that the project does not gain access to dom0, as it should not possess such privileges.
Nevertheless, there are still benefits to this. This will be achieved through an architecture that completely separates the processes from the graphical user interface.
This architecture, which separates the user interface code, allows for modifications and the deployment of improvements without exposing the system to direct security risks (such as the “dot files” found in other systems that are shared among users).
(There are still significant security risks as the ease of changing them could be exploited to spread malicious files.)
As previously mentioned, the two parts will be separated, and here is an explanation of each:
Procedural code:
Its function is to activate the function for each button and ensure that no code contains a security vulnerability.
Languages to be used: Rust, Qubes Admin API(maybe?), salt
Declarative Code:
It is the code responsible for rendering the user interface.
The slint language is used.
There will be three files(slint) already available by default (which have been voted for):
Important Information
Voting took place via this post.
Some of the concepts presented within it are:
(duck = dock)
`I like how large projects often adopt an animal as a mascot, so I think it would be nice to have one for this project as well.
I liked the hermit crab as the mascot.
More information in this post.
Top bar with super dock:
Additional content
(Suitable for advanced users, offering easy access to each “Qube” unit and its status (highly useful when managing a large number of these units).)
More photos:
mac os style:
Additional content
Voted by @tofu,@Gandalfen
(Closely resembles macOS—a design proven to be both effective and visually appealing.)
More photos:(…)
minmalist setup:
Additional content
Voted by @Gandalfen
(Embodies absolute simplicity: featuring a single fixed button and two collapsible menus.)
A message to contributors:
Thank you for your contribution.
Content of this post:
This publication addresses developments at the project level.
list of contributors
These are the current contributors who played a significant role in building the project through their proposals:
These are the individuals who shared the issues they encountered and played a key role in getting the work started:
@menaby0 (I welcome collaboration if you are interested)
(I have not yet compiled a complete list of names)
(The lists will be continuously updated over time.)
Original post
I am trying to improve the user interface myself.
The improvements are as follows:
Fixing the dark mode
Adding the Catppuccin theme
Adding a window tiling mode
Adding a better settings application than the default Xfce one
Of course, including the ability to revert to the original state at the touch of a button
(I am not an expert and have limited time, so I cannot promise a near-term completion date)
(I am trying to develop the project in a way that the Qubes OS team might accept for integration)
Are there any other suggestions for improving the user interface?
Development Stages
That’s all for the first Phase.
Work is currently underway on:
I am going to take a short break from working on this project; I want to learn some other things, but I will resume it soon.










