The reason a dedicated microphone is a real product idea and not just a hardware founder's reflex is signal-to-noise. At the volume where the person beside you cannot make out your words, a laptop mic an arm's length away is mostly recording the room. That is the wall Zhu describes hitting at Nothing: too quiet for the Mac to catch, too loud for the desk next to him [5]. His workaround, holding an earbud in front of his mouth to demonstrate on a video call with Wired, is also a sketch of the competing form factor [5]. The device already in a buyer's ear only needs a whisper mode for the Relay Q's argument to get harder.
What a closer microphone does not fix is everything downstream of the waveform. Relay's engine is Google's Gemini [10], and Wired's reviewer rated its transcription below Google's own Rambler on the Pixel 11, with punctuation it sometimes gets wrong [16]. Of the four things Wired describes asking Relay to do, exactly one is reported without a reliability caveat: the Google Calendar event worked, the Slack skill gave trouble, the Maps link arrived but is called hit or miss, and an emoji request produced the literal words "heart emoji" [23][12][19][18]. No microphone routes a Slack message to the right recipient.
So the thing being asked of a buyer today is not hardware money. It is a system hotkey, Fn by default, in every text field [9], microphone access, and, if the Skills are the point, permission for the app to snapshot the screen each time it activates [13]. Relay says the data sits locally and only transits its own servers on the way to Google's, with nothing retained [14]. Wired still files the arrangement next to Microsoft's Recall on trade-offs [15]. The security review happens in this budget year; the Relay Q arrives in early 2027 [2], on one of the four platforms Relay names, with Windows, iOS and Android still listed as plans [22][6].
For anyone weighing a pilot, the tally that settles it costs a week. Every dictation attempt somebody abandoned, sorted into two piles: gave up because of who was in earshot, or gave up because the output needed more cleanup than typing would have. A team whose first pile is fat has the problem Relay is building for, and its only real question is whether a 2027 delivery date is worth a 2026 permissions grant. A team whose second pile is fat has a model-quality problem, and a microphone at the lips does not touch it. Teams with both piles full should notice which one has a fix that ships now, and it is the software, running on someone else's model, with the accuracy Wired measured [16].
