> For the complete documentation index, see [llms.txt](https://docs.rallyprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rallyprotocol.com/flutter/getting-started/overview.md).

# Overview

## What is RallyProtocol? <a href="#rallyprotocol" id="rallyprotocol"></a>

RallyProtocol is an all-in-one web3 mobile toolkit that enables developers to create end-to-end onchain experiences for native mobile apps. RallyProtocol is comprised of two key components:

## Natively embedded wallets <a href="#natively-embedded-wallets" id="natively-embedded-wallets"></a>

1. Create and store secure, self-custodial wallets natively on-device and in your app.
2. Enable cloud backup for easy recovery.
3. Import and export wallets.

## **Gasless transactions** <a href="#gasless-transactions" id="gasless-transactions"></a>

1. Provide end-users with gas-free onchain transactions.
2. Enable end-users to transfer tokens, claim NFTs, and even deploy smart contracts from within mobile apps gaslessly.

## Supported mobile platforms <a href="#supported-mobile-platforms" id="supported-mobile-platforms"></a>

* Android version 23 and above
* iOS all versions

## Goal <a href="#goal" id="goal"></a>

RallyProtocol serves as a bridge between the intricate world of onchain technology and the familiar realm of UX in native mobile apps. It is designed to empower developers to seamlessly blend in-app experiences with onchain features, reducing web3 friction and enabling them to focus on what they do best—creating delightful mobile apps.

### &#x20; <a href="#mobile-sdks" id="mobile-sdks"></a>


---

# 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.rallyprotocol.com/flutter/getting-started/overview.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.