> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/ja/testing-your-app.md).

# アプリの公開

Adalo でアプリを公開するための操作ガイド

どのプラットフォームで公開するかに関わらず、テストから本番までをすぐに進めるための方法をご紹介します！

## 開始前に

* "**Publsh**"をオンにして、アプリを公開できるようにしてください。

  ![](https://797861279-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EFNSNZLMs5AZ70x2P33%2Fuploads%2Fgit-blob-ebf4864d77764d14052688c6352c5ee7ad65144a%2FScreenshot%202023-08-15%20at%204.09.30%20PM.png?alt=media)
* カスタムドメインに公開するには、***スターター、プロフェッショナル、チーム、またはビジネスプラン*** が必要です。
* Apple App StoreやGoogle Playストアに公開するには、***プロフェッショナル、チーム、またはビジネスプラン*** が必要です。

{% hint style="warning" %}
Adaloのトライアルプランには、ネイティブな公開やカスタムドメインの機能は含まれていません。
{% endhint %}

{% content-ref url="/pages/yRv7pLQLXaDiQlN1dUwE" %}
[Webへの公開](/ja/testing-your-app/publishing-to-the-web.md)
{% endcontent-ref %}

{% content-ref url="/pages/cRjn57KY3SKPBynPHErA" %}
[Google Playストアへの公開](/ja/testing-your-app/publishing-to-the-google-play-store.md)
{% endcontent-ref %}

{% content-ref url="/pages/4O5VtqBNSn5BWN7YB5Kj" %}
[Apple App Storeへの公開](/ja/testing-your-app/publishing-to-the-apple-app-store.md)
{% endcontent-ref %}

{% content-ref url="/pages/3KgpbJAGVj6AyD7K1uqP" %}
[公開に関するFAQ](/ja/testing-your-app/publishing-faqs.md)
{% endcontent-ref %}


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.adalo.com/ja/testing-your-app.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.