VICTOR VANCE 00:00
Strong is not a number. Give me the churn figure and who measured it.
24 AUG 2026
The useful time to find out a plan is wrong is on the walk before the meeting, not at the desk after it. That is what a phone is for here, and it is what this surface does better than a browser on a desk.
What exists today
In development 24 Aug 2026
No date yet. A date goes on this page when it is a commitment rather than a hope.
Store listings
App Store PENDING No App Store listing exists yet, so there is no badge here and nothing to install.
In the browser you already have.
One email, on the day this surface ships, and nothing else. Off unless you tick it, and one click to stop.
19 AUG 2026
What there is to show is the exchange itself, written out below in the form the home page publishes it. Four personas disagree about the same paragraph, the third is cut off mid sentence when the human speaks, and the words are written rather than transcribed from a room. The arrangement of turns is composed, and the chip below carries that.
Not yet produced
A phone with the room on its screen. There is no screen to photograph, and a device frame with a render inside it reads as a screenshot to everyone who sees it.
Not yet produced
The two pictures a store listing shows before you install. A design render is acceptable on our own site when it is labelled. It is not acceptable in a store listing, where it is a policy breach in most stores, so these wait on the real application either way.
RECONSTRUCTION composed arrangement
VICTOR VANCE 00:00
Strong is not a number. Give me the churn figure and who measured it.
DR ELENA ROSTOVA 00:03
It holds until the first bad Tuesday. Then you pay for the outage and the rewrite.
MARCUS THORNE 00:05
There is no precedent, so assume no demand. What does it cost a buyer to
Cut off here
YOU 00:07
Stop. Price the churn first and come back to acquisition after.
You spoke here
PRIYA RAMAN 00:09
Name who ships it. If it is this hard to schedule, it is probably the wrong shape.
Measured
Voice to voice
1471 ms
Median, on the bench in us-central1, with a real media server
MEASURED 2026-08-19, 122 readings
Real human sessions
0 sessions
Have taken place. Every measured turn so far used pre-rendered audio
MEASURED 2026-08-23, 1 reading
There is no screenshot on this page and no device frame with a render in it. A design render presented as an app screenshot is a lie to a reader and a policy breach in the store it would be submitted to, and it is the first thing we would be asking you not to trust us about. The measured figures above are what exists to show. Both sit on the evidence page with the method and the sample size.
A plan gets written at a desk and defended somewhere else. The twenty minutes between the two is when the objections you have not thought of are cheapest to hear, and it is time nobody spends at a keyboard.
A phone is worse than a laptop at everything that happens after a session. The transcript is long, it is attributed line by line, and it is the artefact you actually use afterwards. Reading it in a narrow column on a small screen is worse than reading it in a window, and this page says so rather than leaving it out.
There is no capability table on this page today. A row goes in this block once the capability register records how that capability would be shown to be real, and no row carries that yet. The browser surface carries its own state line and its own account of what it does.
| Requirement | What it means |
|---|---|
| A minimum iOS version | The floor is to be published when the app ships, here and in the listing. A minimum version is a property of the binary that runs, so a figure named ahead of that binary is a figure that moves, and this page and the listing would then disagree about it. |
| Device classes | iPhone is supported. iPad is not supported. Mac is not supported. Apple Vision is not supported. Those four determinations are held in the channel register, so this page and the listing cannot disagree about which device the app is for. |
| Headphones | Strongly recommended and close to a requirement. A phone speaker feeding back into a phone microphone is the worst case of the feedback problem, not the mildest. |
| Microphone permission | The app asks when you join a room, and not at first launch. Refusing it leaves you able to listen and not to interrupt, which is half the product. |
Two more things are on you rather than on the phone, and no setting fixes either of them. A live room is a voice call, so it costs roughly what a voice call costs, and a weak connection costs you audio quality before it costs you anything else. And it is a spoken conversation in which you will be interrupting people, so you need somewhere you can talk out loud. A walk works. A quiet carriage does not.
NOT MEASURED. A 45 minute voice call with continuous audio in both directions is expensive on any phone, and we would rather publish the measured figure once than guess at it now. The method: Xcode Instruments Energy Log against a physical iPhone, screen off and wired headphones, back to back rooms of that length from a full charge, with the battery percentage read before and after each room and published beside the date and the handset.
NOT MEASURED. A room is a voice call, so the order of magnitude is a voice call, and the exact figure depends on the codec the media server settles on. The method: the iOS cellular data counter reset immediately before a room and read immediately after it, on a physical iPhone with Wi-Fi turned off, repeated once per codec the media server offers, and published beside the date, the handset and the network.
Not decided. iOS hands the audio session to the incoming call, so the room loses the microphone whether we like it or not. What we owe you is a defined behaviour on the way back in, written down here rather than left for you to find in the middle of a room.
NOT MEASURED. Bluetooth adds its own latency on top of the voice to voice figure on this page, that figure was measured on a wired path, and interrupting is the part of the product most sensitive to the difference. The method: an audio interface recording the room output and the human microphone onto one timeline, on a physical iPhone, run first with a paired Bluetooth headset and then over the wired path already measured, with the two offsets compared and published beside the date, the handset and the headset model.
Yes, through the mono fallback. You lose the stereo separation that makes the personas easier to tell apart, which matters more here than it sounds: the separation is what stops the first two minutes going on working out who is who.
Not decided. A room that dies when you open your calendar is not a room you can use on a walk, so this is a requirement rather than an edge case, and it is one of the reasons a native app exists at all.
Tingvar does not store your session audio: it is processed while the room is live and no recording of it is kept. What persists is the transcript, the text of what you said and what each persona said, attributed line by line. Only the account that ran the session can read that transcript, and nobody at Tingvar reads one without your written request on a support case. You can delete any session yourself, and deletions are purged from backups within 30 days. The retention schedule is published at tingvar.com/trust/your-data.
IDLE
Zero real human sessions have taken place. Every measured turn to date used pre-rendered audio clips rather than a live human. What is built and verified is the decision layer: the turn-taking policy, the bid scoring and the configuration guards, with 619 automated tests passing and 81.78 % combined coverage. Everything there says the system works. Nothing there says anyone wants it, and being first is a real risk you are taking.