Skip to content
Today
Sign in

Build1 publisherNot yet confirmed elsewhere2 min readPublished

Frappe v16.50 starts retiring the Desktop Icon grid in favour of app-first Desk navigation

Frappe Framework and ERPNext v16.50 start retiring the Desktop Icon grid and move Desk navigation to an App, Module and Sidebar hierarchy. Developer Mohamed Hamed argues in a dev.to guide to the release that new custom-app navigation should target the Apps screen and Dock now.

The Engineer · Build desk

How we use AISend a correction

Illustration accompanying Frappe v16.50 starts retiring the Desktop Icon grid in favour of app-first Desk navigation
Generated illustration

What happened

  • Opening an app puts its modules in the Dock, and opening a module brings up that module's own sidebar of DocTypes, reports, pages, workspaces and dashboards.
  • Sites that already used the Desktop Icon grid keep it after upgrading, with their icons and arrangement retained, according to Frappe's migration documentation.
  • Newly created sites start on the Apps screen instead of the old grid.
  • Frappe plans to remove the grid in a future release, once most sites have migrated.

Compiled by The EngineerSomething wrong?How this is made

Why it matters

  • constraint Removal waits on how many sites have migrated, and no release is named, so app maintainers cannot put a dated deprecation into their own release plans.
  • decision A custom app installed on both new and upgraded sites has to ship module and sidebar navigation, because an entry that exists only as a Desktop Icon has nowhere to show on a new site.
  • cost Administrators of upgraded sites carry the migration work for per-user icon layouts, role-dependent shortcuts, bookmarks and custom Workspace Sidebars before the grid goes.

On v16.50, the home screen a user lands on depends on the site's history [3][5]. An upgraded site that was on the grid keeps it as a fallback while it moves to the Apps screen, so for a while it carries both models [4]. A fresh install has only the new path. For a release that replaces the home screen, the label is modest. Frappe calls v16.50 a polished v16, not v17, focused on navigation and user experience while trying to minimise breaking changes [8].

The account comes from a dev.to guide by developer Mohamed Hamed, published in October 2026, which works from Frappe's migration documentation and the official v16.50 announcement [13]. "This is more than a visual redesign. It changes how navigation should be modeled in a large Frappe application," Hamed wrote [14].

Part of the confusion, Hamed writes, is that one name covers several objects [9]. He separates three. The first is the old home-screen grid. The second is the Desktop Icon records that the grid and the compatibility code still read. The third is the Apps screen, the forward-looking Desktop with one entry per application [9]. According to Hamed, only the grid is what the official documentation calls a retiring fallback [15]. He says the Desktop Icon DocType stays in the framework because Frappe has to support real installations while they migrate. Its presence, he says, is no recommendation to build new navigation on the grid [18].

Hamed's reason for keeping the fallback at all is that ERP installations cannot safely switch navigation models overnight [16]. He applies the same reasoning to the bug reports. Frappe's GitHub history has issues touching Desktop Icons, Workspaces, layout persistence, permissions, caching and Workspace Sidebars. Hamed notes that some were filed during active v16 development and later fixed [12]. "Deprecation and maintenance can happen at the same time," he wrote [17].

I think the sequencing is right in this context. Frappe pays to maintain a compatibility layer it intends to delete. In return, upgraded sites migrate on their own schedule [4]. New custom-app work has one sensible target, the module and its sidebar, because new and upgraded sites both end up on the Apps screen [20].

What to watch

  • Frappe naming a specific release for removing the Desktop Icon grid.
  • Changes to the Desktop Icon DocType or its compatibility behaviour in later v16 point releases.
  • Any Frappe tooling that maps existing icon arrangements onto Apps, Dock and module sidebars.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence50
Adoption
Insufficient
Hype gap−5
Incentives
Insufficient
Confidence55
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Frappe Framework and ERPNext v16.50 introduce a Desk navigation hierarchy of App, then Module, then Sidebar containing DocTypes, Reports, Pages, Workspaces and Dashboards; the old Desktop Icon grid is retiring.

    ReportedSupportedSource: Mohamed Hamed, dev.to, citing the official v16.50 announcementView cited source
  2. [2]

    In v16.50 the Desktop page focuses on applications; after a user opens an app its modules appear in the Dock, and opening a module provides the sidebar associated with that module.

    ReportedSupportedSource: Mohamed Hamed, dev.toView cited source
  3. [3]

    A site already using the Desktop Icon grid keeps using it after the upgrade, and its icons and their arrangement are retained.

    ReportedSupportedSource: Frappe migration documentation, as summarised by Mohamed HamedView cited source

Sources

1 independent publisher whose own reporting we read for this story.

  1. dev.to

    1 article · October 7, 2026

    Frappe / ERPNext v16.50: The Future of Desktop Icons and Desk Navigation

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Create a free account to composeSign in

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Topics

Entities

Loading related stories