> For the complete documentation index, see [llms.txt](https://wp.jannavi.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.jannavi.net/expansion-of-the-jan-navi-ecosystem/market-development-by-jan-navi.md).

# Market Development by JAN-Navi

The JAN-Navi platform and JAN-Navi DAO are exploring two key areas for market development.

<figure><img src="/files/PlHvVvpHmRMKb4luvKrF" alt=""><figcaption></figcaption></figure>

* **Fusion of WEB2 and WEB3 Users**\
  Mahjong is predominantly a WEB2 market. By introducing WEB3 technologies into this economy, JAN-Navi expands the market.
  * Jan-Navi WEB2:

    * Registered: 5.7 million
    * Daily Active Users: 15,000

* **Expanding Mahjong e-Sports**\
  Mahjong has a player base of 900 million, primarily concentrated in Asia, but the economic ecosystem is underdeveloped. JAN-Navi aims to create a global e-sports platform for casual Mahjong play, spreading the love of the game worldwide.
  * e-Sports Total Population: 532 million


---

# 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://wp.jannavi.net/expansion-of-the-jan-navi-ecosystem/market-development-by-jan-navi.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.