> For the complete documentation index, see [llms.txt](https://docs.visiongame.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visiongame.io/visiongame-ecosystem/visionarcade/current-milestones.md).

# Current Milestones

VisionArcade’s journey began two years ago with the launch of our social platform, which has since hosted over 5,000 participants in more than five competitions across five games. This engagement highlights the strong foundation we’ve built for community-driven P2E experiences.

Currently, our focus is on expanding VisionArcade’s reach through a dedicated mobile solution aimed at supporting traditional developers with user acquisition. In addition to this mobile platform, we’re developing three distinct mobile games for the TON blockchain, all slated for release in 2025. These games mark a significant step forward, as we broaden VisionArcade’s offerings and further integrate web3 and mobile gaming.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.visiongame.io/visiongame-ecosystem/visionarcade/current-milestones.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.