Remote desktop peers and details
The main MyDeskViewer view with peer status, connection actions and detailed information about the selected remote computer.
A first look at the current MyDeskViewer Windows interface. Browse the main peer view, remote access settings and the workflow for adding another computer.
Windows desktop interface, with device management, settings and remote-access workflow.
The main MyDeskViewer view with peer status, connection actions and detailed information about the selected remote computer.
Settings for language, machine password, optional preview updates, connection confirmation and remote session timeout.
Add another computer to MyDeskViewer using its Machine ID and optional access password.
Microsoft Store (MSIX) interface: accounts, devices, access and settings.
Start a remote connection using a Machine ID and access password, without signing in.
Manage saved computers, connection status and selected device details.
View and manage this computer’s Machine ID, custom ID and access password.
Adjust interface language, text size and remote-control preferences.
Sign in with Google, Microsoft or your email address.
MyDeskViewer for macOS: guest access, saved computers, settings and encrypted remote sessions.
MyDeskViewer on the complete Linux desktop: sign-in, settings and remote access.
MyDeskViewer on Android: connect without an account, configure your device and view remote desktop sessions.
Screenshots for this platform will be added later.
Screenshots for this platform will be added later.
This page presents the MyDeskViewer interface and the practical workflow around connecting to computers, using saved devices, opening tools and handling daily remote sessions on supported platforms.
MyDeskViewer is being built as a practical remote desktop and device management tool. The main focus is reliable connections, saved devices, clear permissions and an interface that stays usable in everyday work.
The project currently targets Windows first, while Android, Linux, macOS and FreeBSD support continue to grow. The website is meant to explain not only what already works, but also what is being tested and improved right now.
If you want a fuller picture, combine this page with the blog and the change log. Those sections explain why certain functions exist, how platform differences affect implementation and what direction the product is taking next.