> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/platform-guides.md). # 平台指南在任意受支持的平台上部署 Convai Unity SDK——涵盖在 WebGL、iOS、Android 和 XR 头显上发布前需要额外配置的内容。 Convai Unity SDK 适用于 Unity 支持的每个平台。核心功能——语音对话、唇形同步、动作、情绪和长期记忆——无需针对平台进行更改即可运行。不同平台之间变化的是操作系统或浏览器如何处理麦克风访问、音频播放和摄像头权限。这些指南正是围绕这一点：哪些需要额外配置、哪些表现不同，以及在发布前需要验证什么。


Windows、macOS 和 Linux 所有桌面平台均支持完整功能——无需额外配置。屏幕共享仅限桌面端。	Windows、macOS 和 Linux
WebGL 浏览器音频限制、HTTPS 要求，以及首次语音会话前需通过手势触发麦克风激活。	WebGL
iOS 和 Android 发布前请声明麦克风和摄像头权限——遗漏这些权限会导致崩溃和 App Store 拒审。	iOS 和 Android
XR 头显 XR 头显平台概览——核心功能无需额外设置即可运行。包括 Meta Quest 透视 Vision 配置。	XR 头显

--- # 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://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/platform-guides.md?ask=&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.