> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/metaverse/publishing/embed.md).

# Embedding within Apps

## Integration within Apps

Integration within apps works by running the link generated above of an iframe(web) equivalent in the app.

### **Android - Chrome Custom Tabs**

Custom Tabs is a browser feature, introduced by Chrome, that is now supported by most major browsers on Android. It gives apps more control over their web experience, and makes transitions between native and web content more seamless without having to resort to a WebView\.More documentation can be found [here](https://developer.chrome.com/docs/android/custom-tabs/overview/).

{% content-ref url="/pages/H1Szio15DlTAYaRFsOJe" %}
[Android Embed](/metaverse/publishing/embed/android-embed.md)
{% endcontent-ref %}

### **iOS**

There are 2 implementations that can be used namely **WKWebView** and **SFSafariViewController**. Both these implementations are similar to android’s chrome custom tabs implementation but have their own set of use cases. We recommend using SFSafariViewController to run GMetri experiences within your app to get the full immersive experience. Documentation for both can be found here:

* **WKWebView :** [WKWebView](https://developer.apple.com/documentation/webkit/wkwebview)
* **SFSafariViewController :** [SFSafariViewController](https://developer.apple.com/documentation/safariservices/sfsafariviewcontroller)


---

# 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.gmetri.com/metaverse/publishing/embed.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.