> For the complete documentation index, see [llms.txt](https://matheus-draau.gitbook.io/solana-onboarding-kit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://matheus-draau.gitbook.io/solana-onboarding-kit/introduction.md).

# 1. Introduction

The Solana ecosystem, like crypto in general, was built by and for people who already master its rules. Wallets, DEXs, aggregators, and lending platforms assume a user who knows what a seed phrase is, understands self-custody, recognizes *slippage*, and accepts the irreversibility of transactions as a natural condition. For someone arriving from Web2 (from custodial exchanges, digital banks, any product where "I forgot my password" is a button and not a sentence of permanent loss), that assumption is precisely the breaking point.

Onboarding is where this rupture either happens or is avoided. It is the border between the user who adopts and the one who abandons; and, in a financial context of irreversible actions, it is also the border between the user who protects themselves and the one who loses funds for not having understood what they were doing.

This is not just a local impression. Voskobojnikov et al. ([CHI 2021](https://dl.acm.org/doi/10.1145/3411764.3445407)), analyzing 45,821 reviews of the five most popular mobile wallets, found that UX problems lead to severe errors and irreversible financial losses, even among experienced users, and traced the root cause to the absence of clear communication standards during onboarding.

And the failure is structural, not incidental. Every team building on Solana solves onboarding from scratch, in isolation, with no shared reference, so the same action works in a completely different way in each app, and the beginner relearns the basics at every new product. Solana has world-class technical infrastructure: fast finality, low fees, a rich tooling ecosystem. What it lacks is an equivalent **UX infrastructure**: documented, researched, and accessible to any builder. That missing layer is where onboarding breaks.

This investigation started from a practical question:

{% hint style="info" %}
**Where, exactly, does the Solana ecosystem's onboarding fail the beginner, and do these failure points repeat enough to become design patterns?**
{% endhint %}

The short answer is yes. And it is this repetition that justifies the next phase of the work: turning a one-off diagnosis into reusable, systemic solutions.

## The adoption question

But there is a second question, and it is the one that gives economic meaning to everything else:

{% hint style="info" %}
**Can a standardized, reusable entry-point UI/UX system actually move the needle on the adoption of the network's products?**
{% endhint %}

The answer is also yes, and the reason is direct. Every failure we mapped in onboarding is, in practice, a user who gives up before becoming an active user, or worse, who loses funds and never comes back. Abandonment is not a marketing problem solved by bringing more people to the door; it is a product problem, solved by making sure that whoever reaches the door can get through it. Well-resolved entry patterns (seed phrase education, contextual help, inline glossary, gate anticipation) attack exactly the point where the funnel leaks. That is why the design system is not a parallel aesthetic effort: it is the cheapest and most cross-cutting adoption lever the ecosystem has available, because a single well-designed solution replicates across dozens of products that today repeat the same mistake.

***

➡️ Continue to [**2. How the analysis was conducted**](/solana-onboarding-kit/methodology.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://matheus-draau.gitbook.io/solana-onboarding-kit/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.