Near Intents

Claimed positioning:

• The title and meta description position Near Intents as “the smartest way to trade across chains” using an intent + solver model with on-chain execution. That’s a sophisticated narrative aimed at users who care about best execution (price improvement, routing, competition among solvers) and security guarantees.

What the page actually communicates:

• The homepage heading is essentially: > “We’ve moved to near.com”
• The body content is minimal (“Near Intents”), so the product story is mostly carried by the metadata rather than the in-product copy.

Design decision implied:

• PM/Design likely prioritized traffic redirection over educating users on the new primitives (intent submission, solver competition, settlement guarantees). This is a reasonable short-term move during a migration, but it creates a mismatch: the brand promise is advanced, while the visible narrative is thin.

Market position they’re trying to claim:

• Execution layer for swaps across chains (closer to “smart order routing + bridge abstraction”) rather than a full DEX suite (pools, farms, perps). The wording “across any blockchain” aims for broad scope, but without supporting IA/content it reads aspirational.

Top-level nav reveals 4 pillars:

• Trade (/)
• Deposit (/deposit)
• History (/history)
• Account (/account)

What this says about the product:

• This is not positioned as a multi-module DeFi “supermarket.” There’s no Pool/LP, Earn, Perps, or Governance module exposed in navigation. The IA is intentionally narrow and operational, consistent with an execution-first product.

Information hierarchy implications:

• The inclusion of Deposit as a first-class item suggests the PM expects funding friction (cross-chain or wallet readiness) to be a major blocker, so deposit is elevated rather than buried inside the trade flow.
• History being top-level is a trust and debuggability signal: intent-based execution introduces non-obvious states (quotes, partial fills, solver selection, settlement). Surfacing history helps users reconcile what happened.
• Account indicates identity/session management is not purely wallet-native, or at least that there are settings/linked accounts worth surfacing.

What’s missing in IA (by design or by gap):

• No explicit “How it works”, Fees, Solvers, or Security pages from nav. For an intents system, these are usually critical to reduce confusion and improve institutional comfort.

Primary conversion path:

• Land on Trade → Sign in (if gated) → Deposit (fund) → configure swap → submit intent.

CTA strategy observed:

• The strongest CTAs are Deposit and Sign in, which indicates the PM is optimizing for activation (funded, authenticated user) over top-of-funnel education.
• Trade UI CTAs like USDC, NEAR, Max, 50% signal a standard swap interaction model: token selectors + quick amount presets to reduce input friction.

Onboarding pattern implied:

• “Sign in” (vs “Connect wallet”) suggests either:
  • a NEAR account-based sign-in model, or
  • a cross-chain identity abstraction that needs explicit session auth. In either case, it’s a meaningful design choice: it can simplify repeat use, but it adds perceived friction compared to a one-click wallet connect.

Conversion risk:

• With the homepage largely acting as a redirect notice, users aren’t being walked through:
  • what an intent is,
  • how solvers are selected,
  • expected time-to-fill,
  • what “secure, on-chain execution” concretely guarantees.
• The result is a flow that may work for existing users, but likely underperforms for new users who need mental-model scaffolding before depositing funds.

What we can infer from the current surface:

• There’s no visible navigation to Docs, Developer, Audits, Bug bounty, Governance, or Community destinations.
• The only explicit external cue is the migration message: > “We’ve moved to near.com”

PM read on ecosystem maturity signals:

• For an intents protocol, ecosystem signals matter more than average:
  • Users need to trust the solver marketplace mechanics.
  • Builders need APIs/specs to integrate (quoting, intent submission, settlement monitoring).
• The lack of obvious links suggests either:
  • ecosystem resources exist but are not surfaced in this UI, or
  • the product is currently in a transitional state where distribution happens via Near.com rather than the standalone app.

What’s missing for institutional-grade confidence:

• Audit and risk disclosures (what is on-chain vs off-chain, solver permissions, failure modes).
• Status/incident channel for execution reliability.
• Docs that specify intent lifecycle, solver competition, and fee model.

Bottom line:

• The product may be relying on the broader NEAR brand to carry trust, but the app itself isn’t currently doing the work to expose ecosystem depth.

Notable design decisions (good):

• Tight IA (Trade/Deposit/History/Account) matches the likely primary job-to-be-done: get best execution across chains with minimal clicks.
• Elevating History is correct for intents: when execution is abstracted, transparency is the product.
• Quick amount CTAs (Max, 50%) suggest the team is optimizing for speed and repeat behavior.

Where the design currently under-delivers:

• The product story is inconsistent: metadata sells a complex, differentiated mechanism, while the UI surface provides almost no explanation. For intents, users need:
  • Expected execution timing and state transitions
  • Quote vs final fill explanation
  • Solver/route transparency (even if abstracted by default)
  • Fees + guarantees in plain language

What I’d change (high impact, low scope):

• Add a lightweight “How Intents Work” panel on Trade with 3 steps and a link to deeper docs.
• In History, label lifecycle states (Submitted → Solver matched → On-chain executed) and show the key proof points.
• Replace/augment “Sign in” with clearer intent (e.g., Connect wallet / Sign in) to reduce uncertainty.

Benchmark vs best-in-class:

• Best-in-class DEXs pair fast swap UX with trust UX (explainers, audit links, fee disclosure). Near Intents has the fast-UX skeleton, but is missing the trust and education layer that converts new users at scale.