You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the virtual keyboard is off, the remote's input goes nowhere outside the app. Expose the decoded events at the system level so that other applications (media centers, games, home automation, scripts) can subscribe to them and react themselves, instead of relying on injected keystrokes.
This implies shipping a small client SDK plus technical documentation for third-party developers.
Current behaviour
RemotePipeline (src/AppleRemote.Core/RemotePipeline.cs) raises Event (RemoteEvent: buttons, touch) and Gesture (GestureEvent); RemoteSession (src/AppleRemote.Windows/RemoteSession.cs) re-raises them in-process.
The only way out of the app is KeyBinder -> SendInput, gated by RemoteSession.KeyboardEnabled (toggle in Settings), plus software / combination / macro actions.
With the keyboard off, another program has no way to know a button was pressed. SendInput also has known limits: UIPI (elevated windows ignore it), focus-dependent, lossy (a gesture becomes a key).
Expected behaviour
The app publishes every button, gesture (and battery / connection state) on a local IPC endpoint, whether or not the virtual keyboard is enabled.
Any number of local clients can connect, subscribe and disconnect at any time; a slow or crashed client never blocks the remote pipeline.
Optional: an "exclusive" mode where the virtual keyboard stays off while a client is connected (the client takes over).
Implementation notes
Transport: a named pipe (\.\pipe\AppleRemote) with newline-delimited JSON is the simplest cross-language option (C#, C++, Python, Node, PowerShell all read it with stdlib). A localhost WebSocket would add browser clients; only if needed.
Protocol: one JSON object per line, versioned ({"v":1,"type":"button","name":"playpause","down":true,"t":...}, gesture, battery, connected / disconnected). Names reuse KeyMap.Inputs.
Security: pipe ACL restricted to the current user (no remote / cross-session access); never accept commands that inject input or run software from clients in v1 (read-only stream).
Server: lives in AppleRemote.Windows (hooks RemoteSession.Event / Gesture); serialisation and message model in Core (portable, tested).
SDK: a thin AppleRemote.Client .NET package (connect, typed events, auto-reconnect) + a minimal Python sample; other languages use the documented wire format directly.
Activity