Figma desktop overhauls file navigation — small changes, big day-to-day impact
Figma shipped a desktop app update on May 1 that touches three different parts of the file navigation experience. None of the individual changes are headline features, but collectively they're the kind of friction reduction that designers will feel within a week of updating.
What actually changed
First, tab search. The tab overflow menu now includes a search field that filters open and recently closed tabs by name. For anyone who keeps 20+ Figma tabs open across multiple projects, this turns the previous hunt-and-peck process into a one-second lookup. The recently closed list is the bigger win — it surfaces files you had open earlier that day but had to close, without having to dig through file history.
Second, direct link opens on macOS. Clicking a Figma link from anywhere on the system now opens the file in the desktop app directly, skipping the browser routing step that previously added two or three seconds and an unnecessary tab. This was a long-standing complaint and the fix is overdue.
Background preloading
The third change is invisible until you notice it: files and prototypes now preload in the background based on Figma's prediction of what you're likely to open next. Open a project folder and the files at the top of the list start loading before you click them. The result is that the most common files in your workflow are ready by the time you switch to them, instead of producing the usual 1-3 second wait while the canvas hydrates.
The mechanism is opaque from the user side, but the practical effect is that switching between active files feels closer to switching between tabs in a browser than to opening fresh applications. For designers who jump between five or six files in a typical work session, that's a meaningful change.
Why this matters for tool builders
Figma's update is a useful reminder that polish matters more than features for tools designers use every day. The headline-grabbing release notes typically focus on new capabilities (AI features, new node types, expanded plugin APIs), but the changes that actually move daily satisfaction are usually the friction reductions like these.
For anyone building a frontend tool, the takeaway is to track and ship the small friction reductions even when they don't have a clean marketing story. Tab search and direct link handling aren't going to drive a press cycle, but they're the changes Figma users will mention favorably when asked about the app a month from now.