Balancer

What they claim: The meta title and description position Balancer primarily as a multi-network token swap venue (“Swap tokens on Balancer” across Ethereum L2s like Optimism/Arbitrum/Base). That’s a very direct, utility-first positioning.

What’s missing in the visible hierarchy: The homepage text content is effectively just “Balancer”, with no supporting headline, explainer, or benefit-led narrative. From a PM perspective, that’s a deliberate design decision (or an unfinished state): it assumes the user already knows Balancer, or that navigation will do the explanatory work.

Implied market position: The presence of Pools and veBAL in primary nav suggests Balancer wants to be understood not only as a swap UI, but as an AMM liquidity platform + governance/alignment system. However, the brand messaging doesn’t explicitly articulate Balancer’s differentiators (e.g., pool design flexibility, routing efficiency, or LP strategy options).

Net: the product identity is strong for insiders, but the self-description doesn’t do enough to convert “heard of Balancer” into “I know what to do here and why.”

Top-level pillars in nav:

• Swap: primary trader entry point
• Pools: liquidity discovery + LP entry point
• Portfolio: post-action management layer (positions, holdings)
• veBAL: governance + incentives alignment
• Build: developer-facing surface

IA strategy I read from this: Balancer is organized around user jobs rather than protocol jargon:

• Trade (Swap)
• Provide liquidity (Pools)
• Track/manage (Portfolio)
• Participate/lock (veBAL)
• Integrate/extend (Build)

Priority signal: Putting Pools at the same hierarchy level as Swap is a clear statement: LP flows are not secondary; they’re a core growth lever. Likewise, veBAL being top-level (not buried under “Governance”) signals a strong focus on sticky, aligned capital.

Gap: There’s no explicit “Learn” or “How it works” pillar in the primary nav. Docs are relegated to the footer, which is fine for experienced users but creates a comprehension cliff for new users.

Overall, the nav is clean and opinionated: fewer items, more protocol-native pillars.

CTAs: The only visible CTAs are [Create wallet] and [Connect], which indicates the product is optimized for a wallet-first conversion model.

Primary conversion path (implied):

1. Land on site
2. Connect wallet (or create one)
3. Choose a functional page: Swap or Pools
4. Complete transaction
5. Use Portfolio for confirmation/management
6. Graduate to veBAL for longer-term participation

What’s good:

• The inclusion of Create wallet suggests Balancer is trying to reduce dependency on users already being set up. That’s a practical conversion lever for less-native audiences.
• Clear separation between “do” actions (Swap/Pools) and “manage” (Portfolio) supports a predictable journey.

What’s weak:

• With essentially no homepage guidance, the product relies on the user self-selecting the correct workflow. Best-in-class DEX onboarding typically offers choice architecture (“I want to swap / I want to earn / I want to vote”) plus lightweight education.
• No visible pre-connect exploration cue (e.g., “Explore pools” as a prominent CTA) even though it exists in the footer.

The flow is efficient for returning users, but under-instrumented for first-time intent shaping.

Footer breadth is strong and very protocol-native:

• Docs split by version: v3 Docs, v2 Docs, plus “Prototype on v3” signals an active migration and a willingness to expose experimental surfaces.
• Developer trust signals: “Code & Contracts”, “Bug bounties”, “3rd party services”, “Risks” — this is mature DeFi posture (transparency + risk framing).
• Governance stack: Forum + Governance links, and veBAL as a first-class product page. This indicates governance isn’t ceremonial; it’s integrated into the product.
• Analytics integrations: Dune Analytics and Defilytica links imply an expectation that users will validate metrics independently.

Design decision I like: Keeping deep ecosystem links in the footer avoids cluttering the primary nav, while still serving power users.

What I’d still ask for: “Build” exists, but the footer doesn’t explicitly show a developer quickstart or SDK/API entry point at the same prominence as trading links. If “Build” is a strategic pillar, it needs tighter integration with docs pathways.

Ecosystem maturity reads high; the UI just doesn’t surface it early enough in the user journey.

Notable design choices:

• Lean top nav with clear pillars (Swap, Pools, Portfolio, veBAL) indicates disciplined scope and a focus on core protocol loops.
• Wallet-first CTA strategy keeps the experience transaction-oriented and reduces friction for executing.
• Footer governance + risk framing reflects an institutional-grade posture (terms, privacy, cookies, risks, third-party services).

What’s working:

• The IA mirrors how advanced users think: trade, LP, manage, lock/vote.
• Versioned docs (v2/v3) and “Prototype on v3” are good transparency patterns during major upgrades.

What’s missing / improvements:

• Above-the-fold explanation: add a one-screen narrative: what Balancer is, why it’s different (routing, pool design, incentives), and the three primary intents.
• Pre-connect exploration: elevate “Explore pools” and “View portfolio” as browseable, read-only entry points.
• Guided pathways: lightweight wizards for “Earn with pools” and “Get veBAL” to reduce conceptual load.

Against best-in-class DEXs: The structure is solid, but best-in-class products convert better by pairing clean IA with intent-driven onboarding and education rather than assuming protocol familiarity.