Before you begin
Start screen sharing from the conversation composer, then choose the source in the browser’s own permission dialog. A whole display may expose notifications, other windows and sensitive information. Prefer a single tab or window when it covers the task, and check the audience before you confirm. Other devices view the share from its conversation message.
A practical workflow
Shared audio depends on the browser, operating system and selected source. An audio checkbox is not a guarantee that every sound on the computer is available. Mobile browsers may not offer screen capture at all. Stop the share using the browser indicator or Share control when finished, and verify that the capture indicator has disappeared. Screen sharing is live viewing, not a promise of automatic recording.
Screen sharing
Share a screen, window or tab with every connected device for reviews, lessons and demos — peer to peer, like everything else.
Questions that matter
Is screen sharing available yet?
Yes. Use the screen-sharing button beside the message composer and choose a screen, window or tab. Other devices can watch from the chat message. The shared clipboard is still planned.
What is the difference between public and private sharing?
Public sharing reaches connected devices on the current network. Click a device avatar, then choose private sharing to send only to that device. Each conversation has its own messages and file list. Private messages and files are not included in public history or file catalogs.
Which browsers and devices are supported?
Current versions of Chrome, Edge, Safari and Firefox on Windows, macOS, Linux, Android, iOS and iPadOS. The browser needs WebRTC, WebCrypto and IndexedDB, and the page must be opened over HTTPS.
Open the page. That is the whole setup.
OKYA Share uses only standard browser technology, so there is nothing to install or configure.
- Join the same network: Connect your devices to the same Wi-Fi or wired LAN, then open share.okya.app in a modern browser.
- Devices verify each other: A lightweight signaling service introduces candidates. Automatic mode verifies a local host-candidate path; devices attested by a configured LAN node use a separate verification path.
- Share freely: Once verified, files, messages and screens flow directly between devices. Close the tab to stop sharing.
Connection and privacy
Messages and files are sent over WebRTC DataChannels, which are always encrypted (DTLS). TURN relays are disabled by design, so content can never be forwarded through a server.
If automatic local-path verification fails, Share shows a clear message instead of guessing. An optional administrator-run LAN node can attest devices separately; those attested connections may use configured STUN, but never a TURN relay. Network restrictions can still prevent a connection.