> For the complete documentation index, see [llms.txt](https://docs.ndi.video/all/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ndi.video/all/using-ndi/apps.md). # Apps NDI Apps bring the power of NDI technology directly to your everyday devices. From mobile phones and tablets to desktop computers, these applications make it possible to capture, send, and receive high-quality video and audio across standard networks without the need for specialized hardware. Whether you’re streaming a live event, collaborating remotely, or extending the reach of your production setup, NDI Apps are designed to make professional-grade connectivity accessible anywhere. By turning consumer devices into fully functional NDI sources and receivers, these apps help bridge the gap between professional broadcast environments and everyday creative workflows. [**Camera**](https://apps.apple.com/us/app/ndi-camera-easy-streaming/id1477266080) **Capture** (coming soon) ### NDI HX Camera Release Notes 3.1 #### Fixes * iPhone 17 startup crash * Low quality NDI stream not restarting after format change * iOS26 Liquid Glass UI fixes and updates * Locked white balance controls on lenses that do not support it * Various efficiency improvements #### Features * Added PAL and Cinema frame rate support (24, 25, 48, and 50) * Added video rotation override --- # 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.ndi.video/all/using-ndi/apps.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.