Random video chat on mobile works best when the phone stays under your control.
A phone makes spontaneous video easy, but the small screen combines camera, notifications, battery, network and exit controls in one hand. Prepare the device so a dropped signal or incoming alert does not decide the call for you.
WHO CAM / WHOCAM.LIVEAbout this guideChecklistPractical guide
On this page
1
Choose a stable place before choosing a match
Sit or stand where the phone can remain still without revealing passers-by, mail, screens or a precise location. Resting the device near eye level is easier on the other person than walking while the image shakes. Avoid roads, platforms and other places where attention belongs to movement around you. Random chat should not compete with driving, cycling or navigating traffic.
Check what changes when you rotate the phone. Portrait may show more of the room above and below you; landscape may reveal people or objects at the sides. Use the orientation that keeps your face readable and the background intentional. A simple stand or a supported hand usually produces a better conversation than a beauty effect because the image stops moving.
2
Separate site permission from phone permission
Mobile browsers sit inside the operating system’s camera and microphone controls. A site may be allowed in the browser while the browser app itself is blocked by the phone, or the reverse. If the preview fails, inspect one layer at a time rather than tapping Allow repeatedly. The camera-help guide follows this sequence without assuming that every phone uses the same menu names.
Grant only the access needed for the selected mode. Permission is not a promise that recording cannot occur elsewhere, and closing one tab may not remove a permission you told the browser to remember. After the session, confirm the camera or microphone activity indicator has ended and review retained site access if the device is shared.
3
Plan for data use without inventing a number
Live video generally moves more data than text or still images, but the amount varies with duration, resolution, network conditions and product behaviour. There is no verified single megabytes-per-minute figure for a WhoCam call that you can use to budget every session. If your plan is limited, check the phone’s current per-app or browser data view before and after a short controlled call.
A strong Wi-Fi label does not guarantee a good path to the service, and cellular bars do not describe congestion. If the picture freezes, stop other downloads, move closer to a trusted router or try again when the connection is stable. Avoid switching repeatedly between Wi-Fi and cellular during a sensitive conversation because the media session may pause or reconnect unpredictably.
4
Protect the call from notifications and interruptions
Notification previews can expose names, message text, appointments and verification codes directly over the video interface. Use the phone’s focus or do-not-disturb controls where appropriate, but remember that emergency or favourite contacts may still break through depending on your settings. Test the actual state before matching instead of assuming an icon silences everything.
Incoming calls, alarms, low-battery alerts and app switching can move the browser into the background. Know how the product behaves when you return: whether the camera resumes, the match remains active or the session has ended. Do not assume the other participant sees the same screen you do during an interruption. When privacy matters, end deliberately before opening another app.
5
Keep Stop and report within reach
A desktop user can move a pointer across a large layout; a mobile user may be holding the same device that displays the control. Use a grip that leaves one thumb free and avoid full-screen states that hide browser or product navigation you still need. Find the actual call controls before starting; a button that takes you into chat is not the control that ends a conversation.
Before matching, locate Stop, Next, report and block in the real product flow. If a control is covered by the keyboard, browser bar or rotation, return to the supported orientation rather than continuing a harmful call while searching. If you cannot find a way to end the conversation promptly, close the tab and check that the camera indicator turns off.
6
Manage heat and battery as session signals
Camera, screen, encoding and network activity can warm a phone and consume battery. Remove unnecessary background work, reduce direct sunlight and connect to power only with safe equipment. If the device becomes unusually hot, dims heavily or behaves unpredictably, end the session and let it recover rather than treating discomfort as a challenge to continue.
Battery saver modes may change background activity, brightness or network behaviour. The exact effect depends on the phone and system version, so do not assume that a setting which worked on another phone will have the same effect on yours. A reliable five-minute session is more useful than entering with three percent battery and hoping the interface survives an important moment.
7
Reset the phone after leaving
Confirm the call has ended, the activity indicator is gone and the browser is no longer holding a live media tab. Review whether the account should remain signed in. On a shared phone, remove notification traces and saved permission only when you are authorised to change that browser profile; do not erase another person’s settings or history as a privacy shortcut.
The best mobile route is not necessarily the route with the fewest taps. Account, age and permission steps may explain a real decision. Judge each screen by whether it makes the next consequence understandable and reversible. Opening WhoCam chat lets you review the available options. Read the setup screen and use the start control only when you are ready; opening the public page is not a completed match.
8
Make accessibility part of the setup
Increase text or system zoom before entering if labels are hard to read, and check that the larger layout still leaves critical controls available. Use the phone’s built-in hearing, caption or assistive features when they work with the selected browser and media route. Availability varies, so verify the actual call screen instead of treating an operating-system feature list as proof.
Colour, animation and small status dots should never be the only explanation of whether a call is looking, connected or ended. Read the visible state label and keep reduced-motion preferences enabled when motion is distracting. If a label remains unclear at a comfortable text size, pause before choosing an action. Being able to see a button is not the same as knowing what it will do.
9
Test the browser bars before an important session
Mobile browsers expand and collapse their address and navigation bars as you scroll. That changing viewport can move a button, cover a status message or make a full-height panel jump. Before matching, scroll once, return to the top and rotate only if the product supports it. The aim is to learn where the controls settle without discovering the layout during a difficult conversation.
If an installed web app and a normal browser tab behave differently, treat them as separate routes. Permission, sign-in and back navigation may not carry over in the way you expect. Use the route you have already tested, and keep the operating system’s app switcher available. A small screen rewards familiarity more than speed: one calm rehearsal prevents many frantic taps.
Checklist
Phone-ready in under a minute
1Stable position and intentional crop.
2Browser and operating-system permissions checked.
3Sensitive notification previews controlled.
4Stop, Next and report reachable with one hand.
5Network, battery and heat support a short call.
Sources
Further reading from official sources
These references provide context, not an endorsement of WhoCam.
Questions
Before you enter
There is no verified universal figure; duration, media quality, network and product behaviour change usage. Measure a short call in your phone’s current data view if your plan is limited.
Each browser app can have separate operating-system and site permissions.