Why DeskDrawer's boards have no title bar
Most desktop organizers put a title bar on top of each container. Removing it was the first design decision in DeskDrawer, and it drove most of the ones that followed.
The first prototype had title bars, because that is what containers have. It looked professional and it was wrong, and it took a full-screen screenshot to see why.
Six boards on a 1080p display, each with a title bar about 28 pixels high plus its border and padding, spent roughly 200 vertical pixels — near enough a tenth of the screen — on chrome. Those pixels were not showing files. They were showing six copies of the word "Board" and six close buttons for a thing that is not a window and cannot meaningfully be closed.
The purpose of a desktop organizer is to give you more usable desktop. Spending a tenth of the screen to announce that an organizer is present is working against the product's only job.
What a title bar is actually for#
Three things, usually: it names the container, it gives you somewhere to drag it, and it holds controls.
The naming is worth very little here. You know what is in a board because you can see the icons in it; the label matters when scanning a layout you have not looked at for a week, which is not most of the time. Dragging and controls are real needs, but neither requires a full-width strip.
Where the controls went#
Into one compact widget in the bottom-right corner of each board: fold arrow, name, resize grip, on a single line.
The bottom-right corner is the right place because of how icon grids fill. Icons flow from the top-left, and the last row is almost never complete, so the bottom-right cell is usually empty. The controls occupy space that was already unused. A title bar, by contrast, occupies space that is always at a premium: the top, where the first row of icons wants to be.
That gives a smaller, quieter, denser board — the same icons in less area — and the resize grip ends up adjacent to the corner you would naturally drag anyway.
Then the outlines came off#
Once the chrome was one small cluster, the border started looking like the loudest thing on screen, so it became a toggle. With outlines off, a board is nothing but your icons on your wallpaper, and the widget fades in only when the pointer is over the board.
This is the mode most people settle on, and it is the state the whole product is designed around: the tool disappears and the desktop remains.
What it cost#
Three real things, stated honestly:
Discoverability. A control you cannot see is a control you may not find. The widget is in one consistent place on every board, and outlines are on by default so the first-run experience shows where things are — but a title bar would be more obvious, and there is no pretending otherwise.
A conditioned expectation. People expect a container to have a bar at the top. The first few minutes with DeskDrawer involve unlearning that.
Hit-testing precision. Three controls on one line in a corner is a small target area, and it sits on top of a surface that also responds to clicks. Getting this exactly right took two releases: in 1.2.3 clicking the title bar, resize corner or fold arrow in single-click-launch mode could launch the icon sitting behind it, and in 1.2.5 double-clicking the fold arrow or the resize grip could open an icon behind the widget. Both are the same class of bug, and both are a direct consequence of putting controls on top of content rather than in a reserved strip.
That is the honest ledger. A title bar would have avoided two bugs and cost a tenth of the screen, permanently, for every user. It was still the wrong trade.