Byreal — Product Design
Byreal positions itself as an agent-ready Solana DEX with perps and “zero friction” claims, but the IA and conversion paths feel more like a market-ticker portal than a clearly staged trading journey.
1. Brand Positioning & Self-Description
What they say they are:
- The title/tagline combo anchors the product in Solana + DEX + Perpetuals, and the meta description pushes a bolder wedge: “AI agent-native” (built for humans and autonomous agents).
- The promise stack is very aggressive: deep on-chain liquidity, zero gas fees, zero price impact. That reads like a performance brand, not a “community” brand.
What the UI reinforces:
- The homepage content is dominated by a dense, high-velocity market tape (lots of tokens, fast price changes, including memecoins and tokenized stocks like xStocks). This implicitly positions Byreal as a cross-asset trading venue, not just a swap page.
- The secondary headline about earning 5.59% APR on SOL with bbSOL adds a “wealth” layer (earn) to a “trade” brand, but it’s not integrated into a broader story (no clear “Trade / Earn / Manage” narrative ladder).
PM read: The positioning is trying to win on speed + breadth + automation readiness. The gap is credibility scaffolding: if you claim “zero price impact” and “AI agent-native,” the product should foreground how (routing, liquidity sources, agent APIs/permissions) instead of burying it behind market tickers.
2. Navigation Architecture & Product Pillars
Top-level pillars visible in nav:
- Trade → Swap (core spot execution)
- Markets (discovery + price context)
- Perps (derivatives pillar)
- Real Farmers / Farmers (yield / incentive program, branded as an identity)
- Portfolio (post-trade account state)
- More (currently routes to swap, which is a design smell)
Information hierarchy implications:
- The nav puts Swap, Markets, Perps side-by-side, suggesting PM priority is “trader suite,” not a single-funnel swap.
- Having both Real Farmers and Farmers pointing to the same destination creates taxonomy ambiguity. Either “Real Farmers” is a campaign and should live under “More,” or it’s a permanent pillar and should be consistently named.
- “More → /swap” suggests the “More” bucket is unfinished or being used as a layout filler. Best-in-class DEX IA uses “More” for Docs, Bridge, Governance, API, Referrals, Settings—things that reduce header clutter.
PM read: The pillars are reasonable, but the IA lacks a clean mental model:
- Discovery (Markets) and execution (Trade) are separated, which is good.
- Incentives (Farmers) and account (Portfolio) are present, which is also good.
- The naming and grouping aren’t crisp enough to communicate the product’s “agent-native” differentiator or where earn programs fit.
3. User Flow & Conversion Strategy
Primary conversion path:
- The recurring, dominant CTA is Connect Wallet, which is standard for DEX conversion.
- Execution CTAs like Buy / Sell, plus quick toggles like Max, 0.5% (likely slippage), and a price line like “1 MNT ≈ - USDC 0% fee” indicate the product wants users to go from quote → trade without extra pages.
Landing-to-action strategy:
- The homepage behaves like a market scanner: it pushes a long list of assets with prices and % changes. This is optimized for returning traders who already know what they want.
- There’s a parallel “earn” hook: Turbo / Priority and 5.59% APR on bbSOL. This looks like an attempt to capture idle SOL and reduce churn, but it competes for attention with trading.
- Timeframe chips (Minutes / Hours / Days) suggest lightweight charting or performance filters, reinforcing the “active trader” posture.
Onboarding patterns visible/implicit:
- Wallet connect is the key gate; after that, the product likely expects immediate action.
- What’s missing from the surface: a clear new-user checklist (get SOL for fees—even if “zero gas,” users still need funding), swap tutorial, or risk disclosure for perps.
PM read: The conversion design is efficient for experienced users, but for new users, the product needs a stronger guided flow: Pick an asset → Understand fees/slippage → Confirm routing/liquidity → Execute → See portfolio impact.
4. Ecosystem & Community Footprint
What’s present:
- Footer links cover the minimum compliance baseline: Terms and Conditions, Privacy Policy.
- User Guide exists, which is important given the breadth (swap + perps + farming).
What’s not visible (and what that implies):
- No explicit links to Docs for developers, API/SDK, GitHub, or agent integration guides. That’s a mismatch with the “AI agent-native” claim—agents require clear programmatic interfaces, permissions, rate limits, and safety models.
- No obvious governance, tokenomics, grants, or community channels surfaced in the primary/secondary nav. That suggests either (a) early-stage product still focusing on trading UX, or (b) the team is intentionally de-emphasizing governance/community in favor of performance positioning.
PM read: The ecosystem layer looks thin from the product surface area. If the strategic bet is “humans + autonomous agents,” the product should elevate:
- Developer portal + agent SDK
- Audit / security posture
- Status page / incident comms
- Clear program terms for “Farmers” incentives
Right now it reads like a trading app with legal docs, not a platform with an ecosystem.
5. Product Design Assessment
Design decisions that look intentional:
- Pillar split (Swap / Markets / Perps / Portfolio) is the right backbone for a full trading venue.
- The homepage prioritizes real-time market breadth (including xStocks), which is a deliberate choice to compete on discovery and tradable universe.
- Trade execution affordances (Buy/Sell, Max, slippage chip) suggest a PM optimizing for low-latency decisions.
What’s working:
- Clear trader-centric orientation: you can imagine a repeat user landing, scanning movers, and jumping into swap/perps quickly.
- “Earn (bbSOL APR)” provides a retention loop beyond pure trading, which is useful in sideways markets.
Gaps / improvements (highest ROI):
- Clarify IA naming: consolidate “Real Farmers” vs “Farmers,” and make “More” a real utility bucket (Docs, Settings, Referrals, API).
- Make the brand claim verifiable in-product: surface a simple module explaining routing/liquidity, fee model, and what ‘zero price impact’ means (and when it doesn’t apply).
- Agent-native needs product artifacts: dedicated nav entry or footer link for Agent/Developer, with SDK, auth model, and safety constraints.
- Perps onboarding: add risk cues, funding/liq price visibility, and a guided first position flow.
Compared to best-in-class DEXs: IA is close, execution UX seems fast, but the differentiation (agent-native) isn’t yet expressed as a first-class product pathway.