Consent is operational
Identity, grants, duration, stop, pause, and revocation are active session controls—not a paragraph hidden in terms.
Capability comparison
Choose a surface for what it can safely do.
This comparison is within RealLexi Connect. It makes no unverifiable claims about another product, implementation, performance, or security posture.
| Capability | Web browser | Native desktop | Mobile |
|---|---|---|---|
| View an authorized remote display | Development | Target | Target |
| Share a local browser surface | User click | Not needed | Not needed |
| Inject system-wide host input | No | Platform permission | Policy dependent |
| Create a virtual display | No | Windows driver path | Viewer only |
| Hold an enrolled device key | No | Protected local storage | Platform key store |
| Trusted access | Not eligible | Explicit device rule | Policy dependent |
| Visible session stop | Required | Required | Required |
Compare with evidence
Questions worth asking of any remote-access product.
This table states RealLexi Connect design commitments and gives clients neutral questions for evaluating alternatives. It does not guess at another vendor’s implementation.
| Decision criterion | RealLexi Connect commitment | What a client should verify anywhere |
|---|---|---|
| Host awareness | Persistent visible session state, live grants, pause, and immediate local stop are product requirements. | Can the host always see and end control, including trusted access? |
| Permission scope | View, pointer, keyboard, touch, pen, game controller, audio, clipboard, files, recording, and display actions remain separate grants. | Does one approval silently unlock unrelated data or input channels? |
| Service access to content | The control plane is designed for identity, authorization, signaling, entitlements, and content-free metadata—not customer session content. | Can service staff, administrators, or support tooling view or decrypt session content? |
| Platform truth | Unsupported APIs, missing signing, absent hardware evidence, and store-policy limits stay labeled and disabled. | Does the availability claim name the exact operating system, version, hardware, and test evidence? |
| Extensions | Browser and VS Code extensions have narrow local-agent duties; no remote shell, source harvesting, or general proxy belongs in the product. | What can the extension read, execute, forward, or persist? |
| Commercial clarity | Base-plan limits, opt-in add-ons, fair-use relay, release status, and annual billing terms are shown separately. | Are premium features, renewal cadence, quotas, and unavailable capabilities distinguishable before payment? |
Reasons to choose this direction
Constraints are part of the interface.
Unsupported stays disabled
Capability detection and platform status replace buttons whose backends do not exist.
One authenticated transport model
LAN, Wi-Fi, tethering, direct Ethernet, and internet routes use the same narrow session model instead of a remote shell.
Content is not an admin feature
The service coordinates authorization and metadata without a product path for staff screen access.