Devices and browsers
Updated 25 August 2026 Applies to: Web app · iOS · Android · Windows · Browser extension · MCP server
Nothing is installable on any surface yet. Every one of the six is in development and the table below carries the state of each, with the date it was confirmed. When there is a room to open, it opens in the browser first, because that is the surface every other one is a port of.
Where it runs, and where it does not yet
| Name | Status | When |
|---|---|---|
| Web app | In development | 24 August 2026 |
| iOS | In development | 24 August 2026 |
| Android | In development | 24 August 2026 |
| Windows | Not planned | 27 August 2026 |
| Browser extension | In development | 24 August 2026 |
| MCP server | In development | 24 August 2026 |
A surface page states what exists, what does not and what it is waiting on. None of them carries a shipping date, because we have not committed to one we can hold.
What a room needs from your machine
| Requirement | What it means |
|---|---|
| A microphone the browser is allowed to use | The room needs your voice to give you the floor. A refused permission is the most common reason a first session fails. |
| Headphones, rather than speakers | Each persona sits at a fixed position in the stereo field. On speakers that placement collapses and the argument becomes harder to follow. |
| A connection that carries real time audio | Outbound real time traffic has to reach the media server. Some corporate networks block it, and that reads as a room that will not start. |
| A current browser | The audio path is built on interfaces that ship in current versions of the major browsers and are absent from old ones. |
Telling a browser fault from a machine fault
01
Try the browser you are least attached to
A second browser separates a machine problem from a browser problem in about a minute, and it is the first thing we would ask you to do anyway.
What you should see. The same fault twice, which points at the machine, or one fault once, which points at the browser.
02
Turn off the extensions that touch audio or the network
Privacy extensions, meeting recorders and virtual microphones all sit in the path. Any one of them can take a device the room expected to have.
What you should see. A working input level with the extensions off.
03
Move off the network, not only off the wire
A phone hotspot rules out a corporate network in about a minute. It is not a fix, it is a diagnosis.
What you should see. The room holding on the hotspot, which tells you the block is on the first network.
04
Send us what you found
The browser, the version, the device and which of the three steps changed the behaviour. That is enough to reproduce almost anything.
What you should see. A reply that names the cause rather than asking you to try the same three things.
If your device is not on the list
Six surfaces are being built and that is the whole set. There is no seventh in progress, and a surface we have not started is one we would rather name as absent than describe as coming.
A screen reader, a switch device or a keyboard only setup is a different question, and the accessibility statement answers it with the known gaps listed by name rather than summarised.
Still stuck
Write to support@tingvar.com. A person replies within 2 business days, Monday to Friday. Send the browser, the version and the device, and skip the screenshot.