> For the complete documentation index, see [llms.txt](https://docs.avataar.ai/knowledge-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avataar.ai/knowledge-center/developer-documentation/how-to-integrate-avataar-experiences/integration-with-ios-renderer.md).
# Integration with iOS Renderer
## Pre-requisites:
To integrate Avataar's renderer with your ios application, you will need the following equipment as a basic requirement:
* Xcode - Apple's integrated development environment (IDE)
* Ios version : 16 & above
* Camera permission needs to be enabled
## Installation :
Please follow the below steps to install the package in your ios application :
* Add the following permission entry to your app's \`Info.plist\` file:
*Key: \`Privacy - Camera Usage Description\`*
*Value: \`$(PRODUCT\_NAME) camera use\`*
* Next , you need to go to “File” and click on “Add Package…”
* Once the package is added, please search for the following URL and add the package by clicking on the ‘Add Package’ button at the bottom right corner.
[*https://github.com/SoulVisionCreations/avataar-gemini-castor-package*](https://github.com/SoulVisionCreations/avataar-gemini-castor-package)
* The package will be added to your application.
* As a next step, please import the \`GeminiCastorFramework\` module into your Swift file by adding the below code snippet.
*import GeminiCastorFramework*
* You now have to access GeminiView which is exported from the GeminiCastorFramework. Create an instance of the Gemini Renderer by calling \`GeminiView()\`. The \`GeminiView\` initializer takes two parameters:
*Your token (generated on Avataar Apollo/shared by Avataar)*
*Config URL (generated when publishing an asset in Avataar Apollo Configurator)*
## Implementation :
Please follow the below steps to integrate Avataar's renderer with your iOS application:
1\. Create a “NavigationView” and wrap the ‘’NavigationLink’’ package inside it.
2\. Set the navigation style to stack:
*.navigationViewStyle(.stack) \*
3\. Add the below parameters to the ‘’NavigationLink’’ in order to navigate to the GeminiView,
*NavigationLink(*
*"",*
*destination: GeminiView(token: yourToken, configURL : yourConfigURL),*
*isActive: $isActive*
*)*
4\. To enable or disable the view, toggle the \`isActive\` variable. By default, please set the “isActive” variable to false to avoid triggering the view on onload of the application.
## Sample :
Here’s a sample of implementing the Renderer integration post installing the package.
import SwiftUI
import GeminiCastorFramework
struct ContentView: View {
let dummyToken = "your\_token"
let configName = "your\_config\_name"
@State private var isActive = false
var body: some View {
NavigationView {
NavigationLink("",destination: GeminiView(token: dummyToken, configURL: configName),
isActive: $isActive
)
}
.navigationViewStyle(.stack)
}
}
---
# 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.avataar.ai/knowledge-center/developer-documentation/how-to-integrate-avataar-experiences/integration-with-ios-renderer.md?ask=&goal=
```
`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.
