Keep the session moving when Wi-Fi drops

Every trainer has a network horror story. The basement seminar room where the phone shows zero bars. The hotel wifi that collapses the moment forty people connect. The institution whose network blocks anything not on the IT department's allowlist. And every time, the same cold sweat: all the planned interactivity relied on an online service, and without internet, nothing works. That scenario is not inevitable — it is a consequence of architecture. When the session lives on a remote server, the internet is a single point of failure. SnapInteract made the opposite choice: the server is your Mac. It is in the room, with you. Here is what that changes, concretely.

An architectural choice, not a slogan

Technically, here is what happens: when you start a session, your Mac spins up a small local web server of its own. That server is what serves the participants’ page. They scan the projected QR code (or type a short six-character code), and their browser connects… to your Mac, a few metres away. No app to install, no account to create, and above all: no round trip to a data centre hundreds of kilometres away. The quiz answers literally cross the room.

The practical consequence is simple to state: to run a session, local wifi is enough. As long as the phones and the Mac are on the same network — the room’s, the institution’s, or even a hotspot — the session works, whether that network has internet access or not. The basement with no coverage, the corporate network cut off from the outside world, the community hall box whose subscription lapsed: none of these stop you. The product page details this local-first design.

Four scenarios where it changes everything

• The basement seminar room: zero bars of 4G, no wifi to speak of. A simple router or the venue's local network is enough: the Mac serves the session, the phones connect to it, and the interactivity runs as if nothing were wrong.
• Overloaded hotel wifi: forty participants on a captive portal gasping for air. Your exchanges never go out to the internet — they stay between the phones and the Mac, the part of the network that actually holds up.
• The locked-down institution: IT blocks unlisted online services. There is nothing to get approved on the remote-server side: the session lives on the internal network, full stop.
• The trainer on the train: preparation — building the session, importing material, editing activities — works entirely offline. Tunnel or no tunnel, you keep working, and everything is saved automatically on the Mac.

That last scenario may be the most underrated. The evening before a session rarely happens in ideal conditions: a train, a hotel room, an airport. A tool that demands a connection just to open your own content turns every trip into a gamble. Here, your courses, sessions and participants’ answers live in a file on your Mac — for what that means for confidentiality, the article your data stays on your Mac goes into depth.

What if the phones are not on the same network?

Let’s be complete: sometimes the local network cannot be shared. A corporate wifi that isolates devices from each other, participants who can only use their mobile data, a venue with no network to offer at all. For those cases, an optional internet relay exists: it carries the session between the phones and your Mac when they cannot talk directly. It does not store your data at rest — it passes messages along, nothing more. It is a spare wheel, not the engine: in the normal case, everything happens in the room.

That hierarchy matters. Many tools do the reverse: the remote server is the engine, and the offline mode, when it exists, is an amputated version. Here, the full mode is the local mode, and the relay only adds transport. Your activities, your results, your statistics: everything is born and stays on your Mac either way.

The app tells you where you stand — before the room finds out

Good offline behaviour is not enough; you also need to know about it. SnapInteract detects the network state and says so clearly: you can see whether participants can reach you locally, whether the relay is available, and what happens if things change. No emergency diagnostics while forty people wait, phones in hand. You arrive, you check at a glance, you project the QR code. And if you want to verify before the big day, nothing stops you from running a dry-run session at home: the behaviour will be the same.

A training session should never depend on the weather at a server six hundred kilometres away. When the server is in the room, the only possible failure is one you can see — and fix.

What it also changes for mid-session reliability

There is the visible failure — unable to start — and the sneaky one: the session that breaks halfway through. A remote service can slow down, go into maintenance, or lose your session at the worst moment; there is nothing you can do about it, and that is the most infuriating part. When the session lives on your Mac, that whole category of failures disappears: no remote server, no remote-server outage. The shared timer keeps running, the projected timer stays on screen, answers keep coming in. The only links in the chain are in the room: your Mac, the projector, the local network — things you can see and touch.

In practice: your network checklist fits in three lines

First: can the Mac and the phones be on the same network? If yes, you are done — internet or not. Second: if not, the optional relay takes over, quite literally, as soon as a connection exists somewhere. Third: preparation depends on nothing at all — work on the train, on the plane, in a cellar; everything is on your Mac and saved automatically. It is a contingency list short enough to memorise and robust enough to cover the most hostile rooms. The day the venue’s wifi dies at 9:02 am, you will be the only person in the room who is not worried.

Frequently asked questions