> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/more-guides/onboarding.md).

# Onboarding

Guides to assist the onboarding experience of your app

<div data-with-frame="true"><figure><img src="https://284917788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZz9BLmTU9oydDpL3qiUh%2Fuploads%2FwWEFGfOEF0u5iKqLHNbE%2Fonboarding.png?alt=media&amp;token=30a1ef5d-39f7-4422-9228-56d0e2009bbc" alt=""><figcaption></figcaption></figure></div>

A smooth onboarding process is crucial for applications because it directly affects user retention and engagement. Here are a few reasons why it is important:

* **User Retention**: A seamless onboarding experience helps in retaining new users by reducing friction and making it easier for them to get started with the app.
* **First Impressions**: The onboarding process shapes the first impressions of the application. A positive experience can lead to increased trust and credibility.

By prioritizing a well-designed onboarding process, developers can enhance user experience and promote wider adoption of Bitcoin/Stacks applications.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stacks.co/more-guides/onboarding.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.