### What are Circles Mini Apps?
Circles Mini Apps are focused web applications built around Circles.
They are designed to deliver a narrow, task-specific experience rather than a full wallet or a broad product surface.
The core idea is simple: a Mini App should help a user complete one or a few meaningful actions quickly within a Circles-based product experience. Instead of recreating an entire wallet or ecosystem interface, a Mini App focuses on doing one thing well, such as making a payment, joining a group, claiming something, or completing a specific workflow.
### Embedded Mini Apps
In the embedded model, the user opens the Mini App inside the Mini App environment and signs actions directly there using their Gnosis App passkey.
This creates the smoothest user experience because the user stays within a single flow, without switching devices or scanning QR codes. It feels closer to a native Circles experience and allows tighter integration with the Circles host and SDK.
Embedded Mini Apps are typically the right choice when you want stronger integration with the Circles ecosystem, direct wallet interaction inside the app, and better discoverability through store-based distribution.
Example:
{% embed url="" %}
#### Advantages
* Smooth, native-feeling user experience for existing Gnosis App users
* No extra QR scan step for wallet approval
* Stronger integration with the Circles host and SDK
* Better fit for repeat usage and polished product flows
* Can benefit from Mini App store discovery and distribution
#### Disadvantages
* Requires integration with the Circles host environment
* Usually needs more work to support SDK-based wallet flows
* May require store listing or ecosystem-specific distribution
* Less flexibility, especially if you require third-party integrations such as a database, compared to a fully standalone web app
* More dependent on platform-specific constraints and conventions
#### Best for
* Native Circles experiences
* Direct in-app wallet interactions
* Consumer-facing apps that benefit from low-friction UX
* Apps intended for ecosystem discovery and repeat use
### Standalone Mini Apps
In the standalone model, the Mini App runs as a regular web application on a shared screen, kiosk, event booth, merchant checkout page, or standard website. When wallet approval is required, the app can display a QR code that the user scans with Gnosis App to complete the action. Alternatively, it can provide a button that opens the appropriate Gnosis App transaction URL, allowing the user to complete the transaction in Gnosis App and then return to the Mini App flow.
This approach is often easier to deploy because it does not require embedded Mini App integration or store listing. It also gives builders more freedom to use their own backend, infrastructure, and application setup. The tradeoff is that it introduces an extra approval step, which makes the flow less seamless than an embedded Mini App.
Example:
{% embed url="" %}
#### Advantages
* Easier and faster to deploy
* Works as a normal web app without full host integration
* No need for Mini App store listing
* Greater flexibility in backend, architecture, and product design
* Well suited for physical-world setups like booths, kiosks, and merchant flows
* Easier to experiment with custom infrastructure or non-standard app logic
#### Disadvantages
* Less seamless user experience
* Requires an external approval step through Gnosis App
* Adds friction compared to direct in-app signing
* Can feel less native to the Circles ecosystem
* Multi-step flows may slow down fast or repeated transactions
#### Best for
* CRC transfer-related flows
* Event booth experiences
* Merchant checkout flows
* Apps that need custom backend logic or more deployment freedom
---
# Agent Instructions: 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:
```
GET https://docs.aboutcircles.com/miniapps/what-are-circles-mini-apps.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
