Linkside has a deliberately severe design target: starting a screen share should demand about five seconds of active UI work from the host.
That is an interaction budget, not a promise that another person will see your screen five seconds after you have the idea. Page loads, network negotiation, browser permission prompts, choosing the right window, and waiting for the guest all take real time. We do not yet have enough real-world timing data to present five seconds as a measured result.
The number is useful because it makes every extra field and decision defend itself. If a control is not essential to the common path, it should not block that path.
What the five-second target means
With the default room settings, the host’s path is intentionally short:
- Open the create page and select Create room.
- Select the invite-link pill in the session header to copy the URL.
- Paste the link into the conversation you already have with the guest.
- Select Start sharing, then choose a tab, window, or screen in the browser’s picker.
Some of those actions happen outside Linkside, and none guarantees a fixed elapsed time. The five-second test asks a narrower question: how much product ceremony stands between intent and sharing?
The guest gets the same treatment. The invite URL carries the room code, and the join page prepares a random nickname that the guest can keep or change. With the default settings, joining requires a button press, not a Linkside account. If the host enabled a password or waiting room, those safeguards add the expected extra step.
What the target removes
The quickest way to understand the design is to look at what is absent.
- No account gate. Hosts and guests do not create profiles or provide an email address before a room can start.
- No required configuration fields. The create page offers an optional waiting room and password, but the host can leave the defaults alone and create the room immediately.
- No install step. Hosting and joining happen in the browser, without an app, extension, or plugin. Desktop Chrome and Edge are the recommended host experience; Firefox and Safari can host with caveats, while mobile browsers are typically better suited to joining.
- No recording workflow. Linkside does not record or transcribe the session, so there is no recording choice before sharing and no recording library afterwards.
- No meeting history to manage. Rooms are temporary. After a session ends, its live room state passes through a short cleanup lifecycle and is deleted rather than becoming a permanent workspace.
These omissions are not shortcuts around unfinished screens. They define the job: show something live to a few people you trust, then leave no session-content archive behind.
What the target keeps close
Speed also depends on putting the next useful action where it is needed.
A room becomes a shareable URL in one create step. Creating a room makes one request to Linkside’s signaling service. The response includes the room ID, and the app opens the session page. There is no polling screen or separate invitation builder.
The invite stays in the session header. Selecting the invite pill copies the full join link. The same control changes to Copied briefly, so the host gets confirmation without another dialog.
The browser chooses what can be shown. Linkside asks the browser to start screen capture; the browser presents the tab, window, or screen choices. Linkside does not preselect a surface. That preserves a clear consent step even though Linkside does not control its interface or timing.
The media path is peer-to-peer first. Linkside tries to connect the browsers directly with WebRTC. If a restrictive network or double NAT prevents that, it falls back to a TURN relay rather than failing the session. That fallback is encrypted too; the relay routes encrypted packets but does not get the screen or audio in readable form. The STUN and TURN explanation covers the network details without assuming a WebRTC background.
Fast does not mean invisible infrastructure
A short flow should not require vague privacy claims.
The signaling worker necessarily observes that a room exists, roughly when guests join, and how long the session lasts. If a relay is needed, it observes the routing of encrypted packets, and Cloudflare’s edge sees IP-level traffic to the relay endpoints. Neither the signaling worker nor the relay receives readable media content. Linkside does not retain that operational information long-term or connect it to an account identity.
The media itself is encrypted in transit by the browsers on both the direct and relay routes. Linkside does not hold the media keys, record the session, analyse the shared screen, or transcribe the audio.
Those boundaries matter more than calling the product simply “private.” They tell you what the service can observe, what it cannot read, and what does not remain after the room ends.
Where five seconds breaks
The design target cannot remove delays that belong to the browser, the network, or the other person.
- A first screen share may require browser or operating-system permission before the capture picker opens.
- A crowded picker still takes human attention: you need to choose the correct tab, window, or screen.
- Restrictive networks can prevent a direct connection and require the encrypted relay fallback.
- A guest may not open the link immediately, and a password or waiting room intentionally adds work.
That is why a fuller end-to-end walkthrough uses a 30-second target, with clear conditions and caveats. Five seconds is the pressure applied to Linkside’s own interface. It is not a claim about network physics or another person’s response time.
When the target fits
This design is for the moment when showing is quicker than describing: checking a draft, demonstrating a bug, or walking someone through a setting. Scheduled meetings, large calls, recorded demonstrations, and persistent team spaces need different tools and different measures of success.
If the narrow use case is yours, open a room and count the actions for yourself. For the broader product tradeoffs, read what Linkside deliberately doesn’t do.