> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/other/faq/how-does-batch-work-with-smart-televisions-and-connected-televisions.md).

# How does Batch work with smart televisions and connected televisions?

Android TV and Android-based television operating systems can run the Batch Android SDK.

The main use case supported by these very specific OSes is In-app message sending, and it would work as usual in Batch.

{% hint style="info" %}
If you want to use Batch on additional television operators such as Tizen, reach the Support team or your CSM to evaluate potentiel solutions.
{% endhint %}

### Supported capabilities

| Capability                  | Android TV & Android-based TV OSes | tvOS, Tizen, webOS, set-top boxes |
| --------------------------- | :--------------------------------: | :-------------------------------: |
| **In-App messages**         |                 Yes                |          No SDK available         |
| **Profile data collection** |                 Yes                |          No SDK available         |
| **Push notifications**      |     No, OSes do not support it.    |    No, OSes do not support it.    |
| **Inbox**                   |     No, OSes do not support it.    |    No, OSes do not support it.    |

***

### Design In-App messages for television

Television users navigate with a remote, so every message must be easy to dismiss.

* Use the **Banner**, **Modal** or **Image** format, and rely on auto-dismiss. Note that the Banner auto-dismisses after 10 seconds and that this delay is not configurable, while Modal and Image let you set the auto-close timer.
* Avoid action buttons: remote focus navigation differs across television models. Use the message's global tap action if you need the message to be actionable.
* Test on real devices. Rendering and focus behaviour vary between manufacturers.

{% hint style="info" %}
Note that televisions are often shared across family members and are not as personal as phones. In-app strategies should be adapted to this situation.
{% endhint %}


---

# 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://doc.batch.com/getting-started/other/faq/how-does-batch-work-with-smart-televisions-and-connected-televisions.md?ask=<question>&goal=<endgoal>
```

`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.