Repository navigation
Replies: 2 comments
|
I opened #14807 for this. It is your option 2: a Send immediately setting for iPhone voice input, off by default. With the setting on, the checkmark sends the whole composer message through the normal send path. If the send is blocked, the text stays in the composer as a draft. It is waiting for review and is not approved yet, so it may still change. |
0 replies
|
+1 for option 2 (an opt-in "Send immediately" setting). I'd also like the same setting on desktop once composer voice input lands there (#14814), so dictation behaves the same on every client. Most of my dictated prompts go out unedited, so the extra Enter or tap is just friction. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
When I dictate on the iPhone app, sending takes two taps. I tap the checkmark, wait for the transcript, then tap send. Most of the time I don't touch the text, so that second tap is just me waiting.
I know the review step is on purpose. The voice input notes say transcription only edits the draft and never sends. I'm not asking to change the default. I'm asking if there's room for an opt-in way to skip it.
Two ways it could work:
I'd go with the button. You choose per message, and nothing changes for anyone who doesn't tap it. A setting works too if you'd rather keep the toolbar as it is.
Either way, it should never send when nothing usable came back: no speech, a draft that changed during transcription, a cancel, or an error. If the send is blocked, say uploads are still running, the text just stays in the box.
Earlier attempts:
Would you take either of these? If so, which one?
All reactions