Vercel Redesigns Project Cards: Denser Layout, Smart Widgets
28 Jul 2026
Vercel is quietly reworking one of the most-used surfaces in its dashboard: the project card grid. The changes trade some information (like branch names) for density and introduce a new customizable widget system—an approach worth watching for any founder designing their own dashboard UI.
What changed
According to the report, Vercel reduced the padding and vertical space of each project card. The payoff: one extra row now fits in the grid, meaning users see more projects at a glance without scrolling.
To make room, Vercel removed branch information from the cards entirely. The stated rationale is that most projects use "main" as their default branch, so displaying it adds little value for the majority of users. The Real Experience Score remains the only metadata still shown directly on the card.
Vercel is also testing a change to the card's shortcut context menu, currently gated behind a feature flag. As a mitigation for potential discoverability loss, the same context menu actions have been added to the project's detail view via a standard dropdown menu—giving users a fallback path to the same actions.
The new widget area
The most structurally significant change is a new widget area designed to show dynamic, customizable metadata on each card. Widgets themselves were redesigned from a single-row layout to a two-row layout, allowing more room for data and better spacing.
Alongside this, Vercel revised its widget switcher. The switcher now lets users preview data from other available widgets without permanently changing what's displayed on the card. It also does double duty as a feature-discovery tool: when a project has no data for a given widget, the switcher surfaces an overview of platform features the user hasn't yet enabled.
Risks and trade-offs
The report flags two open risks with this redesign:
- Discoverability: Moving context menu actions behind a feature flag or into a dropdown could make them harder for some users to find, even with the detail-view fallback in place.
- Lost context: Removing branch info could hurt users whose projects don't default to "main"—a minority case the redesign appears to have deprioritized.
Sources do not provide dates, version numbers, or the size of the test population exposed to the feature-flagged context menu changes. There's also no data yet on how these changes affect user engagement or task completion, and it's unclear what other metadata types beyond Real Experience Score will eventually populate the widget area.
Why founders should care
This is a product-design case study more than a funding or market story, but it's one that likely applies to many early-stage teams building their own dashboards:
- Vercel's willingness to trim useful-seeming data (like branch names) in favor of density suggests that information hierarchy decisions are probably worth revisiting periodically as products mature and usage patterns become clearer.
- The modular widget system—paired with a switcher that previews data without committing to a layout change—is a pattern founders could plausibly adapt for their own customizable metadata displays, especially in B2B SaaS dashboards where different users care about different metrics.
- Testing UI changes behind a feature flag, while backstopping potential discoverability loss with a fallback (the dropdown menu), reflects a cautious, incremental rollout strategy. Teams shipping frequent UI changes may find this a reasonably low-risk way to validate design bets before full rollout.
- The widget switcher's secondary role—surfacing unused platform features to users with no data—hints at a lightweight, low-friction onboarding mechanism. Founders looking to improve feature adoption without adding intrusive tooltips or tours might consider similar in-context nudges.
As with any single company's internal design change, it's uncertain how broadly these specific choices will generalize, and no engagement metrics are yet available to confirm the redesign's impact. But the underlying patterns—density trade-offs, modular widgets, and flag-gated testing with fallbacks—are likely to resonate with founders iterating on their own product dashboards.