Local Peer Chat
Move messages and files directly between nearby browser peers.
Some collaboration is most useful when it can happen directly between two connected devices. HYiYH Local Peer Chat provides a browser-native WebRTC path for messaging and file or backup transfer. Signaling and connection setup remain explicit, and the feature is separate from Cloud Chat and its server-side retention model.
What it does
A focused surface with connected context.
Direct WebRTC connection
Connected peers exchange supported data through the browser peer connection rather than uploading each transferred file into HYiYH Cloud storage.
Bounded conversation state
Browser transcripts and transfer buffers use finite limits so an open peer session does not grow memory indefinitely.
Backup handoff
Supported local backup payloads can be moved directly to another connected peer as a portability workflow.
How it fits into a day
Practical workflows, not feature checkboxes.
Connect intentionally
The user establishes the peer session before messages or files can move.
Keep Cloud Chat separate
Cloud Chat remains an authenticated server feature with its own membership and retention policy.
Fall back gracefully
When WebRTC is unavailable or blocked by the network, ordinary file export remains the portable fallback.
Start from the problem instead
See how this feature fits into a real workflow.
The HYiYH solution guides begin with common friction—digital overload, scattered project context, private Body planning, local-first work, professional operations and cross-device workflows—and show which features work together to reduce it.