VoiceDebrief iOS / reviews / round-2

Review, round 2: what the fixes changed

14 November 2026. The same four users, the same tasks, new pictures, after the fixes that followed round 1.

The pictures

Run 19 of screens.yml on the branch work/screens, commit 4338ea2, which holds dev up to 6475ff7: 33 pictures in each of four sets, 132 in all, in the artifact screens-4338ea2367dc8a9c4495c5b3d5257302f23aacce. Everything shown is invented sample data, as before.

What the pictures can show now that they could not in round 1:

Every iPhone screen in the round, light appearance, as one contact sheet

Every iPad screen in the round, light appearance, as one contact sheet

Method

As round 1: the agent first, then four synthetic users, each a separate agent given a persona, a task and only the iPhone pictures that person would see. None was told what round 1 found or what had changed. Each was told that every picture is a separate launch, so that the artefacts of round 1 (times a minute apart, a vault with a different id in each picture) were not reported again. What a user reported was checked against the code before it was written here.

Did the four users change their minds?

UserRound 1Round 2
Records while drivingThe second memo was blocked: the control was greyNot blocked. Read "1 more waiting" and understood there was no need to wait. Still loses a tap, because stopping opens a note
Careful about privacyWould not dictate a confidential noteWould, without pressing Send or adding a server. Decided by "Nothing is sent without pressing it" and the vault saying "On this device only"
Wants to see every requestBlocked: the log shows no host, status, time or causeThe same. Nothing in the log or the Lab changed
Lost a recording elsewhereWould not trust it: a recording said to be kept could not be playedTrusts it to capture: the interrupted note shows a player and "00:00 of 02:12 · 4.2 MB". Would still not make it the only home of a recording, for a new reason: no copy off the phone that an ordinary person can make

Round 1's findings, one by one

#Round 1 findingRound 2Status
1A recording cannot be played; an interrupted one shows no lengthA player on every note with audio, with its length and size, and a line of the transcript plays from that moment. Seen on note.finished, note.transcript, note.interruptedfixed (issue 029)
2No new recording while the last note is written upThe record control stays green; the caption says "The last note is being written up, 1 more waiting"; a waiting note's row says "Waiting its turn". Seen on record.working, libraryfixed (issue 030)
3"Send to The developer" is the most prominent control and says nothing about itselfNow "Send to the developer of this test build", outlined instead of filled, with a line beneath: what goes, that it is encrypted to the recipient's key, that sending to the developer asks first. The confirmation is pictured and names the key. Not shown on an interrupted note. What is left is in the new findingsfixed in the main; the rest stays in issue 031
4"£4.85" on the first screen reads as paying per memoUnchanged. All three users who see the record screen reported it againopen (issue 032)
5The log cannot tell a server from the device; local reads are "Requests" and "Downloaded"Unchanged: "Requests 18, Downloaded 1.6 MB" on a vault that needs no network. The privacy user noticed that 1.6 MB is the size of the recordingopen (issue 033)
6The gist is not first on a noteThe one sentence is the note's heading, with the date beneath; the clean text experiment has moved below the transcript. The send bar still covers the key points on an iPhonefixed (issue 034); the bar is a new finding
7Lists as wide as the window on iPadA note, the Library, Settings, Diagnostics, About, Recipients, Credit and the Lab are held to a readable width. The Vaults screens and the log are not yetfixed in part (issue 035, the vaults session)
8States with no next step or no dayRows read "Interrupted: open it to run it again", "Too short to summarise", "Waiting its turn"; Recent says "Yesterday"; the record screen says "Saved as you speak" before recording; Settings says a note that was interrupted is saved once it has been run againfixed in the main (issue 036); small things remain
9A vault, for someone who has never met oneUnchanged. Both non-technical users again read the end of a note as a doubt about whether it is savedopen (issue 037)
10The control to finish is a green tickUnchanged, and the driver expected a red stop againopen, the owner's decision
11Requests to the model are visible only in the LabUnchangedopen (issues 013, 020)
12"sgit clone followed by this key" gives no commandUnchangedopen (issue 037)
13"Machine arm64"; the language as a codeThe language is named everywhere. "Machine arm64" remains, and may be the simulatorfixed in part
14Rows that wrap or cut badly"1 line" is right; a cut title ends with an ellipsis. In the Library a title is still cut in the middle of a word ("pictu…", "plot ni…") where Recent cuts at a word, and an interrupted row's state runs to a third linefixed in part
15What the pictures could not showThe confirmations, a queued send, a queue of notes and a note on the Record tab are pictured. Not yet: the Lab after a run, a vault with a server, a recipient added by hand, portrait on iPad, the largest text sizefixed in part (issue 038)
16Artefact: a note being made shown under LibraryRemoved: it is pictured on the Record tabfixed
17 to 19Artefacts of separate launchesStill so; the users were told, and did not report themnot a fault
20"No confirmation before sending, deleting or discarding"The three confirmations are pictured, and the users read themfixed, and see new finding 3
21Artefact: no speech model on a simulatorStill sonot a fault

New findings

Most serious first. "Who" is D (driver), P (privacy), V (developer), L (lost a recording), A (the agent).

#ScreenWhoFindingOwnerStatus
1note.finished-end, vaultsLThere is no plain way to get a recording off the phone. A note's words can be shared; its audio cannot be exported or saved to Files. The only other copy is a vault "On this device only", and the route beyond that is a form asking for a server address and an access token. It decided this user against keeping a recording only heremain session; vaults sessionopen, issue 039
2diagnostics-endP, V, AThe "Lane" section on Diagnostics says a link pasted there "is used instead" of the built-in one when a note is sent. Checked in the code: since recipients replaced the lane section on a note, nothing reads that link. A screen says the app does something it does notmain sessionopen, issue 041
3note.finished-send, note.finished-delete, record.recording-discardL, P, DEach confirmation shows one button, the destructive one, and no visible way to back out. The code gives each a Cancel; the pictures do not show it, and three users said they could not see how to say nomain sessionopen, issue 040
4note.finished-sendP, VThe confirmation names the key and not the server that carries the note, nor who "the developer" is, how long it is kept or whether it can be taken backmain sessionopen, with issue 031
5note.finished, note.queuedD, P, AThe send bar and its two lines of small print take about a fifth of an iPhone screen and cover the key points; the "Add" control beside it is cut off at the right edge, leaving half an iconmain sessionopen, with issue 031
6settings, note.finished-endP, L"Save each finished note to a vault" is on by default and does not say there that the vault is on this phone, nor whether a vault that has a server sends by itself. A note does not say whether it is already in a vault; neither does the confirmation before deleting, which says only that "a copy saved to a vault stays"vaults session; main sessionopen, with issue 037
7note.working, record.workingDStopping opens the note, so a second memo straight after costs a small tap at the top corner first. The owner asked for the note to open at once; recorded for a drivermain sessionopen, no issue: the owner's decision, to be watched on a device
8note.queuedPA send pressed early goes the moment the note is finished, before its debrief has been read. It is what issue 026 asks for; the screen says "Will be sent to The developer as soon as it is finished" and offers Cancelmain sessionnot a fault: a decision. The capital in "The developer" is a slip
9record.working, libraryL, AA time just after midnight prints as "0:03" beside "12.0 s" and reads as a length. Lengths are "49.0 s" in a row and "00:49" in the playermain sessionopen, with issue 036
10note.interruptedL, D"Transcribe and debrief again" on a note that was never transcribed; "replaces this note's transcript and debrief" made one user fear for the recording; "Tap a line of the transcript to hear it" where there is no transcript; the row in a list shows no length though the note has onemain sessionopen, with issue 036
11about, identityPNo one place lists everything that can leave the phone. "There is no account yet" on About sits beside "the same Apple account" and iCloud Keychain on Identity; device backups are not mentioned anywheremain session; identity sessionopen, with issue 037
12record.recordingLNothing says how much has been saved so far: a timer shows that time passes, not that the file growsmain sessionopen, with issue 036

What worked

Unprompted, in round 2: "Saved as you speak" before the first recording; "If the recording is cut short, what was said is kept"; the interrupted note with a player and its length; "1 more waiting" under a live record control; a note that opens with its one sentence in bold; a confirmation before sending that names the key, which the developer matched against the fingerprint on Diagnostics; and "Throw this recording away? It cannot be brought back", which the least trusting user called honest.