Your browser is the meeting place.
You do not need a native app to try video chat. A compatible browser, working camera and microphone, and a network that permits media connections are the essentials.
Permission is a deliberate step
Browsers protect camera and microphone access behind permission prompts. On a public website, those features require a secure HTTPS connection. Only grant access when the page and request are what you expect.
If permission is denied, the page cannot simply turn your camera on. You may need to change the site's permission in your browser settings and try again. Another app using the camera, an operating-system restriction, or a disconnected device can also prevent capture.
Direct WebRTC has real network limits
Video media travels directly between browsers. STUN helps discover possible network routes; it does not relay media or hide your network address. The other participant may learn your network address from the direct connection.
There is no TURN relay or fallback. Firewalls, restrictive NAT, or network policy can block the direct route, so video may fail even when matching succeeds. Connection attempts can also fail because of browser, device, or network problems; a successful match is not a promise that media will connect.
Troubleshoot without oversharing
Check your preview, the browser's selected devices, and whether the microphone is muted. Try headphones to reduce echo. If a connection repeatedly fails, stop the session before trying another network or browser; text chat is another option.
Do not paste connection logs, session tokens, device identifiers, or network addresses into a conversation with a stranger. If you contact support, describe the device type, browser, and approximate time instead.