> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/android/guides/collab/sample-firebase.md).

# Realtime collaboration code sample with Firebase

Experience real-time document collaboration with Firebase using the demo below. Run the native sample app conveniently in your browser with Appetize.io. For the best experience, install and run the ap

The demo shown below is an emulation of the document collaboration sample with Firebase app. The demo itself is powered by [Appetize.io](https://appetize.io/) which allows us to conveniently run our native sample app in the browser, however for the best experience you should install and run the [document collaboration with Firebase](https://github.com/ApryseSDK/pdftron-android-samples/tree/master/CollabFirebaseSample/) sample app on a local device. You can perform realtime collaboration with the showcase collaboration sample below and the WebViewer demo here: [WebViewer Demo](/web/collaboration/collaboration-samples.md).

{% embed url="<https://appetize.io/embed/vtuwz305x9g5aqpc3mfmr9rc6w?device=nexus5&scale=95&autoplay=false&orientation=portrait&deviceColor=black>" %}


---

# 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.apryse.com/android/guides/collab/sample-firebase.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.
