ZAYEED preview
Home / Delivery

Open rooms and assessed sittings

An audience-response tool is optimised for friction approaching zero: no account, no install, nothing permanent, and the host improvising a question thirty seconds before asking it. A formal examination seat is optimised for the opposite — the candidate identified, the content delivered before the exam began, the clock unable to be bought back by closing the lid, and an evidence trail that survives an appeal. Zayeed does both, and not by compromising between them.

One engine, two delivery contracts

There is no exam build and no polling build. A school that runs a Friday poll and a mock GCSE runs the same installed binary, and the same .mcq file can be delivered either way. The mode is chosen per sitting.

Exactly three things differ between them: what is required before a sitting may start, what is recorded while it runs, and what is kept when it ends. The grader, the item model, the pack format, the session reducer and all four shells are shared in full. A feature that cannot be expressed as a difference in those three lists does not belong in either mode.

Why this matters more than it sounds. Forking into two products would double the surface that has to be held identical — and the moment a poll and an exam are marked by two different code paths, the score from one stops being evidence about the other.

A room, joined from the phone already in their hand

A pack you own opens as a live room with a six-character code. Everyone else needs a browser and the code.

What the projector structurally cannot show

The relay can be the laptop at the front

A live room is the one part of this product that needs a server — it is a relay between screens, and there is nothing to relay offline. That server does not have to be ours.

Rooms are ephemeral either way. A room lives in the memory of whichever relay is running, and is never written to a database. Restarting that relay ends every room in progress — deliberate for a poll about salaries, and worth knowing before a keynote rather than during one.

What it does under load

A claim about capacity that has not been run is a guess. One thousand simulated phones answering five questions each against a single relay: every answer acknowledged, every acknowledged answer counted, the slowest answer of five thousand at 40ms, and no snapshot at any point carrying another participant's identifier. That test runs against the shipped relay, not a special build, and it runs in the same suite as everything else.

Pictures, recordings and film

A picture that fails to draw fails in front of the candidate, who can see it has failed. A recording that fails to play fails silently, and a candidate cannot tell a broken clip from a clip of silence. That asymmetry drives every decision here.

What plays where is a property of the machine, not of us. Every shell can run the check itself from its account screen, before an exam rather than at the door, and recorded runs are published as recordings — a platform nobody has run it on is printed as not run, never as assumed fine.

What an appeals panel reads

Lockdown, named honestly

Three levels, and each one ships the list of what it cannot do — on screen, before anybody relies on it.

The per-platform truth is printed rather than averaged: Windows excludes the window from capture; Android uses FLAG_SECURE and screen pinning, and says so when pinning is refused because the device has no management profile; a Linux desktop on Wayland is not permitted to suppress screenshots or inspect other windows, so Supervised there is Focused plus display detection, which the app states instead of quietly downgrading; and a browser tab cannot block screenshots, see other windows, or stop another application being opened — for a paper that needs those, install the app.

The limit no software escapes. None of this can see anything outside the window: a second device, a phone under the desk, or another person in the room. A camera pointed at the screen defeats every screenshot restriction on every platform, including the ones that do not say so.

What this does not claim to be

A test centre is operations, not software, and a product that implies otherwise gets caught out. There is no camera proctoring, no identity verification, no biometric check-in, no network of invigilated seats, and no third-party proctor integration. What is here is the software half: a paper that arrived before the exam did and could not be read early, a clock that cannot be bought back, a sitting that refuses to start on a machine that cannot play it, and an attempt that can prove what it was.

Still deciding?

Run a paper with a recording in it, then run the same pack as a room on your phone. The two are the same file and the same marker.