> For the complete documentation index, see [llms.txt](https://kazarhq.gitbook.io/kazarhq-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kazarhq.gitbook.io/kazarhq-docs/problems/problem-statement/poor-onboarding-and-experience-friction.md).

# Poor Onboarding and Experience Friction

Web3 gaming often fails before the game even begins. For players, the journey starts with wallet connections, token approvals, network switches, and unexplained gas fees. For new  users, these all terms are like being lost in a jungle.

But it’s not just players who suffer. **Developers, too, face enormous UX challenges**. Building seamless Web3 experiences requires stitching multiple walletSDKs, bridges, token contracts, backend logic, and marketplace layers, **most of which are not built for games.**

The result?

* **Players drop off before onboarding completes**—over 70% never return after their first session.
* **Developers are forced to either compromise on UX or spend months building basics**, slowing innovation and wasting resources.

Without smoother tools and infrastructure, *<mark style="color:red;">**Web3 gaming remains too clunky to attract players and too complex to retain builders.**</mark>*


---

# 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://kazarhq.gitbook.io/kazarhq-docs/problems/problem-statement/poor-onboarding-and-experience-friction.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.