> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-android-client-guide/v19/tips-and-tricks/work-with-remote-apps-on-big-screen.md).

# Work with Remote Apps on Big Screen

Sometimes working with applications on a small screen is inconvenient, especially when you have to scroll the app window left/right/up/down, select or tap small GUI elements, or type a lot of text...

But now, starting from version 17.1, Parallels Client supports the Samsung DeX feature (it was first included on Galaxy S8 smartphones). So if you use a Samsung mobile device with DeX support, you can work with Parallels Client, remote apps and desktops either in the full-screen mode or side by side with other Android apps on a big display (you can use an external monitor or TV).

<figure><img src="https://4030289229-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdE26aPb472s8cuV4JFhy%2Fuploads%2FJgIfmkcVal7EQLusg6TC%2Fdex1.png?alt=media&amp;token=414750bd-0024-458e-bcf8-00b597724783" alt=""><figcaption></figcaption></figure>

To make the desktop experience even more convenient for you, the Parallels engineers implemented support for keyboard and mouse. Now you can type in remote apps using the keyboard, click or right-click various GUI items with the mouse and scroll page content with the mouse wheel.

You can also use system shortcuts (e.g., "Alt + Tab", "Windows + D", etc.) while working with remote apps and desktops. When you press them on the keyboard connected to the DeX Station, they are not intercepted by Android.

And that's not all - if you need to go somewhere, take your mobile device with you. Parallels Client smoothly switches between the DeX and phone modes without interrupting your working session.


---

# 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.parallels.com/landing/ras-android-client-guide/v19/tips-and-tricks/work-with-remote-apps-on-big-screen.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.
