> For the complete documentation index, see [llms.txt](https://help.twinr.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.twinr.dev/app-analytics/acquisition-and-retention/session-by-platform.md).

# Session by Platform

Identify the distribution of sessions across different platforms, such as iOS & Android.

This helps you understand the user base and prioritize platform-specific optimizations.

<figure><img src="/files/PSrZbtuXs0urP8JX5juc" alt=""><figcaption></figcaption></figure>

Here in the image, we can see:

* Sessions generated by Android and iOS for current period(5 Dec to 3 Jan) are 361. The selected timeframe here is 30 days.
* 243.81% shows the comparison of previous period from current one.
* 114 sessions are generated from iOS devices and 247 sessions are generated from Android devices in current selected period.


---

# 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://help.twinr.dev/app-analytics/acquisition-and-retention/session-by-platform.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.