Virex Insights

Product writing, updates, trust pages, and the broader company story around owned repos.

UpdatesEarly April 20265 min read

Early April 2026: a cleaner control surface across the whole workspace

This update was about shell quality and hierarchy, not a deep engine rewrite. The dashboard used to feel like stacked blocks. The goal here was to turn it into one premium control surface built around the main actions you actually use.

updatesproduct

The shell moved toward a top-nav product layout

The primary in-app shell now leans toward a horizontal top navigation structure with grouped sections and dropdown-ready organization instead of relying on the older left sidebar as the main navigation model.

That change makes the workspace feel more deliberate on desktop while also giving smaller laptop, tablet, and mobile layouts a cleaner responsive collapse path.

  • Brand stays anchored top-left.
  • Main product sections are visible sooner.
  • Navigation hierarchy is clearer without needing a tall icon rail.

Dashboard hierarchy is tighter and easier to scan

The dashboard was restructured so the thin status strip, core actions, Stripe surface, active projects, milestones, and live feed each have a clearer role.

Instead of every section competing at the same weight, the main actions sit higher, Stripe is more visible near the top, and support surfaces take up less visual space.

Stripe is treated as a real dashboard feature

Revenue readiness and Stripe setup now have a more prominent home in the upper dashboard instead of feeling like optional setup noise. That matters because monetization visibility should stay near the builder workflow.

The current surface is intentionally graph-ready and keeps room for deeper connect and revenue expansion without forcing another dashboard redesign later.

Milestones and live feed became smaller support layers

Milestones still stay visible, but they no longer dominate the page. The live feed also moved into a quieter support role so the dashboard feels active without turning noisy.

This helps the product feel more premium because the hierarchy is driven by action and momentum, not by how many large blocks can fit on screen.

Technical cleanup was part of the phase

The update also includes some technical cleanup, such as removing the duplicate Next config split and aligning the repo more closely with a push-safe structure.

The aim is not only visual polish but a cleaner baseline for the next dashboard and engine phases.