# Circles Mini Apps Launchpad

The Circles MiniApps Launchpad is designed to encourage practical applications that help people do meaningful things with Circles. Selected projects will be highlighted through recurring recognition cycles such as **App of the Week**, **Winner of the Month**, and themed bounty rounds.

The goal is simple: expand the Circles MiniApps ecosystem with apps that are useful, testable, and relevant to real users and communities.

MiniApps can focus on areas such as payments, community coordination, local commerce, events, group use cases, public goods, mutual aid, games, tools, and experimental social-money experiences.

***

### Who Can Participate?

The program is open to all kinds of builders. You do not need to be a protocol expert to participate.

#### Beginner Builders

If you are new to development or new to Web3, you are welcome to participate. You can build simple Circles-enabled apps using starter kits, payment links, QR flows, and basic on-chain confirmation.

Use of AI tools is allowed and encouraged, especially for participants with little or no prior coding experience.

#### Web Developers

Frontend and full-stack developers can build polished MiniApps using React, Svelte, Next.js, or similar frameworks. Apps with a strong user experience, clean interface, and practical flows are encouraged.

#### Web3 Developers

Builders familiar with wallets, smart contracts, Gnosis Chain, indexers, RPC APIs, and event-driven app logic can create deeper integrations with the Circles ecosystem.

#### Community Builders

People building for local groups, cooperatives, events, mutual-aid networks, merchants, communities, or Circles groups are encouraged to submit practical tools that solve real coordination problems.

#### Designers and Product Builders

You do not need to write deep protocol code to participate. Useful user journeys, onboarding flows, payment experiences, community tools, and product prototypes are all welcome.

***

### Program Format

The Circles MiniApps Builder Program is a rolling bounty program with recurring recognition and rewards.

#### App of the Week ( $500 )

Every week, we will select one standout submission as **App of the Week**.

The selected app will be highlighted publicly and receive a $500 reward.

Weekly winners may include simple but useful apps, strong prototypes, polished user experiences, or creative uses of Circles MiniApps.\
\
Submissions upto Sunday 12:00 GMT will be considered for that week.

#### Winner of the Month ( $1,000 )

Every month, we will select the strongest app submitted or meaningfully improved during that month.

The monthly winner will receive a $1,000 reward.

For the monthly prize, the evaluation will consider not only the app itself but also its traction, usefulness, audience, and potential impact in the Circles ecosystem.\
\
Submissions upto last day of the month 12:00 GMT will be considered for that month.

{% hint style="info" %}
We encourage all participants to join the [Circles Builder Telegram](https://t.me/about_circles/499).
{% endhint %}

***

### What You Can Build

Participants are encouraged to build apps that help people use Circles in practical and meaningful ways.

Example app ideas include:

* Payment tools for merchants, events, or communities
* QR-based payment experiences
* Local commerce and marketplace tools
* Community coordination apps
* Group treasury or group payment tools
* Event check-in or ticketing flows
* Public goods and donation tools
* Mutual-aid coordination tools
* Games or social-money experiments
* Tools for Circles groups and organizations
* Dashboards, explorers, or analytics tools
* Onboarding flows that make Circles easier to understand and use

These are only examples. Builders are encouraged to experiment and submit new ideas.

***

### Eligibility

* Anyone can participate.
* Teams are allowed.
* All submissions must be publicly hosted on GitHub and released under an open-source license.
* Existing apps can participate if they add meaningful new Circles MiniApp functionality.

***

### Submission Requirements

To be eligible, your app must follow the rules below:

* The app must include a real Circles-related feature.
* The app must be testable by reviewers.
* The app must not mislead users about payments, recipients, or transaction outcomes.
* The app must not ask users for seed phrases or private keys.
* The app must clearly show the payment amount and recipient before sending users into a wallet flow.
* The app should avoid collecting unnecessary personal data.
* The app must be publicly available on GitHub with an open-source license.

Submissions should include enough information for reviewers to understand, run, and test the app.

A strong submission should include:

* A short description of the app with a clear explanation of how it uses Circles
* A link to the GitHub repository
* A live demo link, if available
* Screenshots or a short demo video (highly recommended)

***

### Repeat Participation

Builders can submit multiple apps over time.

You can also resubmit meaningful improvements to an existing app.

A previous weekly winner can still be eligible for a monthly or future prize if the app improves meaningfully, gains traction, or adds important new functionality.

The program is designed to reward continuous building, iteration, and real usage.

***

### How to Submit?

To submit you mini app, fill this form with all the details - [Submission Form](https://forms.gle/4Zw77qz1oAzgjVnv9)

Each submission should include the app details, GitHub repository, demo link if available, and a short explanation of how the app uses Circles.

If you are building an embedded-style MiniApp, you should also contribute to the [Circles MiniApps repository](https://github.com/aboutcircles/CirclesMiniapps) and add your app through a pull request. <br>

***

### Resources & Examples

Use the following resources to get started:

* Circles MiniApps documentation: <https://docs.aboutcircles.com/miniapps>
* Circles MiniApps GitHub repository: <https://github.com/aboutcircles/CirclesMiniapps>
* Circles SDK MCP - [https://context7.com/aboutcircles/sdk](https://context7.com/aboutcircles/sdk/)&#x20;

Embedded Mini Apps

* <https://circles.gnosis.io/miniapps>

Standalone Mini Apps

* [https://miniapps.aboutcircles.com](https://miniapps.aboutcircles.com/)

{% hint style="info" %}
If you need any technical help or need any help, feel free to reach out to us on [Discord](https://discord.gg/BcffB9NhM) or on [Circles builder TG](https://t.me/about_circles/499).
{% endhint %}

***

### What We Are Looking For

The best submissions will be useful, understandable, and easy to test.

Production-ready does not mean the app has to be complex. A small app that solves a real problem clearly is often better than a large app that is difficult to use.

Reviewers will look for:

* Practical usefulness & Potential for real-world usage
* Clear Circles integration
* Good user experience
* Safety and transparency around payments
* Open-source availability
* Ease of testing
* Community relevance
* Meaningful iteration over time

***

This program is for anyone who wants to explore what people can do with social money, community payments, and local coordination tools.

Whether you are building your first MiniApp, experimenting with a new idea, or creating a production-ready tool for a real community, you are welcome to participate.

Build something useful. Submit it. Improve it. Help grow the Circles Mini Apps ecosystem.


---

# 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/circles-mini-apps-launchpad.md?ask=<question>
```

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.
