I feel compelled to document my findings after conducting a structured, albeit frustrating, evaluation of the BeyondTrust Remote Support mobile application (Android v. 2024.x). My primary use case, and the one I suspect is relevant for many fellow administrators, is the ability to perform urgent, granular administrative tasks while away from my primary workstation. The marketing suggests parity with the desktop client, but my benchmark—a series of standardized, reproducible workflow tests—reveals critical performance degradations and functional omissions that render it unsuitable for real admin work.
I devised a controlled test suite, timing each operation on both the desktop client (Windows, v. 2024.x) and the mobile app on a high-end tablet over a consistent 5GHz Wi-Fi 6 network. The workload simulated a common crisis scenario: diagnosing a service failure on a server.
**Test Workflow & Latency Results (Avg. over 10 runs):**
* **Session Launch to Interactive Desktop:** Desktop: 2.1s ±0.3s | Mobile: 8.7s ±1.2s (The mobile UI introduces multiple unnecessary taps and a confusing session browser).
* **Execute `Get-Service -Name BITS` in PowerShell:** Desktop: Instant | Mobile: 4.2s ±0.5s (Keyboard invocation lag and poor auto-complete).
* **Navigate to `HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices` in Registry:** Desktop: 1.5s | Mobile: **Failed** (Registry editor is not present in the mobile feature set).
* **Transfer a 50MB log file from remote machine to local storage:** Desktop: 11s (saturates link) | Mobile: 23s (transfer dialog lacks progress granularity and pauses on background).
Beyond the raw latency, the UI/UX is antithetical to precision. Attempting to right-click a taskbar icon to launch Task Manager is an exercise in frustration, as the long-press gesture is inconsistently recognized. The "quick access" tools are not configurable, and key administrative modules like the integrated command line lack the ability to predefine common scripts or commands. It feels like a viewer, not a tool.
My conclusion is that the mobile app serves only as a *monitoring* terminal—perhaps usable to check if a session is active or to perform a simple reboot. For any administrative task requiring interaction with system utilities, registry, advanced file transfer, or command-line interfaces, the throughput and functionality are insufficient. The development resources would have been better spent refining the PWA or accelerating the HTML5 client's feature parity. Until the mobile app receives a fundamental architectural review and a feature set matching the desktop client's administrative capabilities, I cannot recommend it for its implied purpose.
-- bb42
-- bb42
Your structured approach is refreshing, and I think it highlights a tension in product development. The marketing promise of "parity" often means feature parity on a checklist, not parity in practical efficacy for different roles.
Your specific timing on session launch gets at a core UX problem: mobile interfaces are often just shrunken desktop ones, ignoring how admin workflows differ on a touch device. I'd be curious if the latency you observed in executing commands is due to the app's rendering engine or something more fundamental like input lag. Have you tested with simpler commands, like a basic `dir` or `ls`, to see if the delay scales with complexity?
Let's keep it real.