7.4.1 UX on Terra Classic post-crash is an ecosystem experience, not a single product experience

On mature L1s, the “user experience” is shaped primarily by a small set of official, consistently maintained surfaces: an official wallet, an official explorer, canonical docs, and a stable set of RPC/LCD endpoints. Terra Classic’s post-crash reality is structurally different:

• There is no single “official” product surface that can enforce consistency across onboarding, wallet flows, app discovery, and support.

• Most user-facing surfaces are community-maintained and therefore subject to discontinuities: ownership changes, funding gaps, volunteer fatigue, and fragmented standards.

• UX outcomes are downstream of governance and treasury execution (covered in Chapter 6): inconsistent resourcing produces inconsistent product quality.

Implication: UX debt on Terra Classic should be assessed less like “a UI polish problem” and more like a coordination + maintenance + distribution problem.

7.4.2 The “front door” problem: discovery surfaces overstate readiness

A core UX failure mode is the mismatch between marketing-like claims and operational reality.

Evidence from the ecosystem directory experience (as shown in the provided screenshots):

• The ecosystem hub messaging suggests “everything you need to explore, build and stake” and advertises “102+ projects” as a headline number.

• In practice (per Chapter 7’s inclusion criteria and Chapter 7.2), a large share of those “projects” are:

  • inactive or unmaintained,

  • infrastructure listings (not applications),

  • unlaunched efforts,

  • or niche/community tools with unmeasurable adoption.

Why this is UX debt (not just narrative):

• New users interpret “102+ projects” as choice and momentum.

• The actual experience often becomes: broken links, inactive dApps, thin liquidity, and inconsistent wallet support.

• That produces a trust shock early in the funnel: users churn before they ever reach “real usage.”

Interpretation (supported by observed mismatch):

• Terra Classic currently exhibits ecosystem theater risk: the discovery layer optimizes perception of breadth, not probability of successful onboarding.

7.4.3 Wallet layer fragmentation is a primary adoption limiter

Wallet UX is the highest-leverage surface in an L1. If wallets are fragmented, users experience Terra Classic as fragile—regardless of chain stability.

Based on the provided wallet listings and operational context:

• Primary day-to-day wallets in practice:

  • LUNCDash (web wallet; also positioned as an “on-chain native” surface in the ecosystem directory screenshots)

  • Galaxy Station (community-maintained wallet surface)

  • Keplr (widely used multi-chain wallet with Terra Classic support)

Additionally:

• “Rebel Station” should be treated as deprecated/legacy in the directory context (per the correction request).

• Terra Station should not be represented as the “default” UX anchor if it is not actively maintained in the Terra Classic context.

Governance-backed operational stewardship signal:

• A governance/operations narrative exists around Hexxagon managing key platforms like Galaxy Station and Galaxy Finder (delegation framed as ecosystem support).

UX impact of wallet fragmentation:

• Inconsistent feature parity: staking, governance voting, IBC handling, token discovery, contract interaction, and signing UX differ by wallet.

• Support ambiguity: users do not know “where to report bugs,” which is fatal in crypto UX.

• Security ambiguity: fragmentation increases phishing surface (lookalike domains, fake extensions, fake app store listings).

• Retention hit: users don’t form habits if the core toolchain changes, breaks, or disappears.

7.4.4 Infrastructure UX debt: endpoints and reliability warnings are baked into the documentation

Infrastructure is part of UX because it determines whether actions work reliably.

Evidence from the Terra Classic documentation UX (from the provided screenshots of the public endpoints page):

• The docs explicitly warn that public infrastructure is intended for development and light workloads, and that production users should run their own node or purchase dedicated access.

• Multiple endpoints are listed across LCD/FCD/GRPC/RPC, with different providers and network IDs.

Why this matters for normal users (not only developers):

• When endpoints rate-limit, degrade, or go down, users experience:

  • slow wallets,

  • failed transactions,

  • broken dApp loads,

  • and “it’s not working” moments that look like chain failure even when the chain is fine.

Why this matters for builders:

• Builders cannot rely on consistent performance if the baseline is “public infra is for light workloads.”

• This raises the cost of shipping production apps: teams must either run infra or pay for it—often without a stable funding path.

Interpretation:

• The ecosystem’s UX debt includes a hidden tax: every serious product must rebuild baseline infrastructure reliability that other L1s provide as a default.

7.4.5 Explorer and analytics surfaces are real, but the experience is not unified

Terra Classic has functioning tooling, but it is not unified into a coherent, predictable “standard stack.”

Evidence:

• There are community-run explorer stacks such as Terra Classic Finder (open-source repository; derivative of Cosmos Explorer).

• Ecosystem directories list multiple analytics tools (e.g., LUNC-focused dashboards) with varying UX maturity.

UX impact:

• Users must learn multiple interfaces to answer basic questions:

  • “Did my tx succeed?”

  • “What’s the fee model?”

  • “Where is liquidity?”

  • “What’s the real staking APR?”

• Each extra tool adds friction and increases abandonment.

Interpretation:

• The issue is not “lack of tools,” but lack of consolidation + standards + canonical flows.

7.4.6 App discovery UX: “scroll fatigue” replaces guided onboarding

In the provided ecosystem UI, categories like wallets, bridges, tools, and developer resources are presented as long lists with mixed states:

• Some items are native to Terra Classic.

• Some are “supported by Terra Classic.”

• Some are inactive or unclear in operational status.

UX debt pattern: unranked lists.

• A directory that does not rank by “likelihood of success for a new user” produces:

  • choice overload,

  • wrong first clicks,

  • dead-end flows.

Minimum viable fix (UX policy, not UI polish):

• Introduce success-path curation:

  • “Start here (Beginner)”

  • “DeFi (only apps with measurable liquidity/volume)”

  • “Builders (only actively maintained repos + working endpoints)”

  • “Legacy / deprecated (do not use)”

7.4.7 Bridge UX: availability is listed, but user risk is not explained

Bridges are high-risk surfaces. Listing them without a risk model is UX debt.

From the screenshots, bridges are presented as a set of options (IBC/bridge partners). The UX gap:

• Users are rarely told:

  • which bridge routes are most reliable,

  • which assets are liquid on the destination,

  • and what the failure modes are (stuck transfers, wrong memo, wrong network).

Implication:

• Terra Classic’s bridge UX increases support burden and raises the probability of early catastrophic user errors.

7.4.8 A practical “UX debt register” for Terra Classic (what is broken, not what is ugly)

This report treats UX debt as systemic friction that blocks adoption, not subjective aesthetics. A high-signal UX debt register for Terra Classic includes:

1. No canonical wallet stack

   • Multiple “main” wallets, inconsistent maintenance posture, unclear defaults.

2. Directory inflation

   • Project counts optimized for perception rather than successful onboarding.

3. Unranked resource lists

   • No success-path guidance; high bounce and confusion.

4. Infra warnings baked into docs

   • Public endpoints positioned as non-production, pushing reliability burden downstream.

5. Support topology is unclear

   • Users do not know which team owns which surface.

6. Brand and trust fragmentation

   • Multiple identities and domains; phishing risk increases as coherence decreases.

7. L1 offers limited product affordances

   • When the core “product” is staking, user journeys are shallow and churn-prone (reinforced by Chapter 7.1).

7.4.9 What the evidence implies: UX debt is a growth constraint, not a cosmetic issue

The combined evidence supports a clear conclusion:

• Terra Classic provides many links to many things, but the ecosystem does not reliably provide a guided, low-risk, high-success onboarding path.

• The most visible UX surface (ecosystem directory) signals abundance (“102+ projects”), while the measurable app layer is small (Chapter 7.2), producing a credibility gap.

• Wallet and infrastructure fragmentation push complexity onto users and builders, increasing churn and reducing the probability that new users reach repeat behavior.

Strategic implication:

• Without a coherent “default stack” (wallet + explorer + endpoints + curated app set + support ownership), Terra Classic’s UX will continue to underperform even if individual dApps improve—because the funnel remains leaky.

Operational implication (ties back to Chapter 6 treasury execution):

• UX improvement is not primarily a UI redesign; it is a governance-funded operating program:

  • define the default stack,

  • fund maintenance and QA,

  • reduce fragmentation,

  • publish deprecation policy,

  • and measure onboarding success.

Investor implication:

• UX debt increases the gap between off-chain speculative interest and on-chain retention. In practice, that keeps Terra Classic in a mode where attention spikes do not reliably convert into sustained users.