> ## Documentation Index
> Fetch the complete documentation index at: https://docs.startale.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mini Apps overview

> Ship your project as a Mini App inside the Startale App. Same wallet, less plumbing, native distribution.

A Startale Mini App is a web application that runs inside the Startale App on mobile and desktop, in an embedded frame. It uses the host's wallet, has access to user STAR Points, and can read the user's verified linked EOAs.

Mini Apps follow the [Farcaster Mini App](https://miniapps.farcaster.xyz) specification, with Startale-specific extensions documented here.

<Note>
  **Protocol foundation.** Startale uses the Farcaster Mini App protocol as a technical communication standard, not as a social platform. Users do not need a Farcaster account to use your Mini App. Farcaster social features (sign-in with Farcaster, cast composition, social graph) are not available inside the Startale App. The protocol provides the iframe communication standard and manifest format only.
</Note>

## Why ship a Mini App

| Build a Mini App when                              | Stay a standalone application when              |
| -------------------------------------------------- | ----------------------------------------------- |
| Your audience already lives in the Startale App    | You need cross-wallet support beyond Startale   |
| You want to read user STAR Points or verified EOAs | You need full control of the auth layer         |
| You are running a campaign with Startale           | You require a non-EVM stack                     |
| You want native distribution in the explorer       | You have an existing user base outside Startale |

## How a Mini App differs from a standalone application

* Authentication is shared with the Startale App, no separate sign-in.
* The wallet popup is replaced by the host's approval UI.
* The signer is always the user's smart account; linked EOAs are read-only.
* A handful of EIP-1193 methods (`wallet_switchEthereumChain`, `wallet_addEthereumChain`) are not available inside the host.

See [Wallet integration](/miniapps/wallet-integration) for the full surface.

## What you ship

1. A web application served over HTTPS.
2. A signed manifest at `/.well-known/farcaster.json`.
3. An `fc:miniapp` meta tag on shareable pages.
4. A submission to Startale.

## Reusing a Farcaster or Base manifest

If your project already lives on Farcaster or Base, your existing `farcaster.json` works on Startale. Add Startale-specific fields inside a `startale` object within your existing `frame` object. A single file works on all three platforms. See [Manifest](/miniapps/manifest).

## Get started

<Columns cols={2}>
  <Card title="Quickstart" icon="rocket" href="/miniapps/quickstart">
    Build, sign, register, and run a Mini App in the local sandbox.
  </Card>

  <Card title="Manifest reference" icon="file" href="/miniapps/manifest">
    Every field, what is required, what is optional, what gets used.
  </Card>

  <Card title="Preview your Mini App" icon="eye" href="https://app.startale.com/developers/preview">
    Load any URL in the Startale App frame and test the wallet handshake.
  </Card>

  <Card title="Developer tools" icon="wrench" href="https://app.startale.com/developers">
    Manifest validator, embed validator, and Mini App preview in one place.
  </Card>
</Columns>