Roadmap

No dates are given here, because a one-person product cannot honour them and a roadmap with dates it misses is worse than none.

Updated 8 August 2026

Current priority: correctness over features#

Most releases have been stability work, and that is still where most of the effort goes. A tool that hides your desktop icon layer and handles your files earns feature work only after it is reliable. Eight rounds of code audits on a small app, and what each one found describes what that has involved.

In the next update#

Built and being tested, not on the Microsoft Store yet. It will ship as 1.3.1 — no date is promised here either.

  • Folder boards. Turn a board into a real folder on your desktop: the folder is named after the board, the board's files move into it, and the board shows what is inside, marked by faint diagonal stripes. Drag icons in and out to move the files; turn it back and they return to the desktop. Files move only when you ask, through the standard Windows file operation, and nothing is overwritten.
  • Shortcut arrows on shortcut icons, as on the Windows desktop, with a tray-menu toggle to hide them.
  • A file made with the desktop's New menu opens straight into rename on its board.
  • New boards appear on the monitor your mouse is on, and resizing snaps flush against neighbouring boards.
  • Fixes, among them a freeze when pointing at a Recycle Bin that holds a very large number of items.

Being considered#

Not commitments — things that are genuinely open.

  • Better display-change handling. Board rectangles are stored in screen coordinates, so moving a configuration between machines with different monitors needs a manual tidy-up. Storing positions relative to a display would fix it. See Layout & monitors.
  • An ARM64 build. Nothing in the design prevents it; it is a packaging and testing question.
  • Accessibility for board contents. Boards are custom-painted, so a screen reader sees nothing useful. Exposing them through UI Automation is a substantial piece of work and it is the limitation that most clearly excludes people.
  • Localized application strings. The interface is icon-driven so the surface is small, but error text is English. See Languages.

Unlikely#

  • Automatic filing rules. Repeatedly requested, and still the feature most likely to move a file somewhere its owner did not choose.
  • Cloud sync of layouts. Would require an account, a server and network access, ending the claim in Privacy & data. Copying config.json already works — see Backup & restore.
  • A portable build for end users. The Store version is signed, updates itself and uninstalls cleanly.

Permanently out of scope#

These will not happen, and saying so is more useful than leaving them open:

  • A plugin or extension system — nothing third-party is ever loaded into this process
  • Theming engines, docks, widgets, wallpaper management
  • Replacing or extending File Explorer
  • Global keyboard hooks
  • Any telemetry, analytics or crash reporting
  • Advertising, or a free ad-supported tier

How to influence it#

Open an issue or send an email — both are on Support. With no telemetry, requests and bug reports are the only signal there is, so they carry real weight. See Shipping with no telemetry, and what it costs.