How to cast to a screen without installing an app

Why casting usually needs a download

Most wireless presentation systems were designed for one room, in one company, where everyone works there. That assumption shows up the moment a visitor tries to present. The receiver on the wall expects a specific sender: a desktop app, a mobile app, or a USB button that gets passed around the table.

For an internal team that is fine. IT pushes the app once and nobody thinks about it again. For a hotel, a venue, a co-working space or a conference, it is the whole problem. The person who needs the screen is someone you have never met, they are on their own laptop, they do not have admin rights on it, and they have four minutes before their session starts.

So the download becomes a queue at the front of the room.

The three ways to cast without an app

Built-in mirroring

Apple devices have AirPlay, and Windows has Miracast. Nothing to install, because the sender is already part of the operating system.

The catch is coverage. AirPlay is an Apple story, Miracast is a Windows and Android story, and neither reaches everyone in a mixed room. If half your guests are on a MacBook and half are on a Windows laptop with a locked-down build, built-in mirroring solves half the room.

Casting through the browser

Every device in the room already has a modern browser, and browsers can now capture a screen, a camera and a microphone with the user's permission. That makes the browser the one sender that is genuinely universal.

This is the approach Soljacast uses. A guest opens a page, picks what to share, and it appears on the display. There is nothing to install because the thing doing the sending is the browser they already have open.

A receiver box on the display

Whichever sender you use, something has to be attached to the screen to receive it. That is usually a small device on HDMI. What varies is what the box demands of the guest: some require their app, some require a button handed across the table, and some just give them a URL.

The box is not the interesting part. What it asks of a stranger is.

What "no app" has to mean in practice

"App-free" is claimed more often than it is delivered, so it is worth being specific about what to test.

Ask whether a guest can do all of the following without installing anything:

• Share their laptop screen, with system audio
• Put slides or a PDF on screen
• Play a video file or a YouTube link
• Use their phone camera as a live input
• Do it on macOS, Windows, Linux, Android and ChromeOS

Plenty of systems clear the first item and fail the rest, so the guest ends up installing something anyway for the one thing they actually came to do. If you are evaluating options, our comparisons go through how the main systems handle each of these.

Setting up a screen anyone can present to

The setup itself is short. Plug the device into power and into the display over HDMI, connect it to the venue Wi-Fi once, and it boots into your branded splash screen from then on. First-time setup usually takes under five minutes.

After that, a guest connects in two steps:

1. Join the device's Wi-Fi from a phone, tablet or laptop.
2. Scan the QR code shown on screen, or type the short URL into any browser.

The same cast page loads either way. From there they pick a source and start sharing.

Worth knowing: local casting works with no internet at all. Screen share, files, camera and web pages run entirely on the device, which matters in basements, older hotels and anywhere the guest Wi-Fi is unreliable. Live translation and YouTube playback are the exceptions, since both need a connection.

Keeping control of who casts

The obvious objection to a QR code on a screen is that anyone can scan it. That is sometimes exactly what you want, and sometimes the opposite.

There are three modes worth having:

• Public, where anyone on the venue Wi-Fi can join by scanning. Good for co-working lounges and casual spaces.
• PIN-gated, where the session needs a code. Good for a room with a door and a scheduled agenda.
• Admin-only, where a single operator controls what goes on screen. Good for a stage, a keynote or anything with an audience.

The failure mode to avoid is a system that only supports one of these. A venue needs different answers for the lobby screen and the main stage.

When an app is still the right answer

Being honest about this matters more than winning the argument.

If every person who will ever present is an employee, the app gets deployed once by IT and then disappears into the background. A native client can also do things a browser tab cannot: deeper conferencing integration, multiple people sharing into a tiled layout at the same time, and tighter control over encoding.

If your rooms are internal meeting rooms with internal staff, an app-based system is a reasonable buy, and some of them are very good at it. The case for browser casting gets strong when the people using the screen keep changing.

The short version

If guests are casting, the sender has to be something they already have. In a mixed room, that is the browser.

Test any system by handing it to someone who has never seen it and watching whether they install anything. That is the only benchmark that matters, and it takes about a minute.

If you want to talk through how this would work in your rooms, get in touch and we will tell you honestly whether it fits.