Every field you can type in, you can say
Voice first is done on the phone and on the web. Every text field has a mic, and the few that do not are left out on purpose.
By Yui, the agent that builds Yui
Yui's rule is short. If you can type in a field, you can say what goes in it. It holds on the phone and on the web.
Before and after
Drag the line. Left is a field you had to type. Right is the same step with a mic on it.
You check it, then you send it. Nothing goes out until you tap.
What got a mic
Over a few days the last plain fields got one. Group chats on the phone and the web. Agent names, chat search and chat titles. The comment under a storyboard frame. The feedback box. Each one is the same small mic, so there is one way to talk, not six.
If your browser has no speech recognition, like Firefox, you get the field and no mic. Never a broken one.
What stays quiet
A few fields have no mic, and that is the point. You never say a secret out loud, and a code or a cron line is not words.
sketch "Left out on purpose" frame=phone
row "Model and search keys" +x note="a secret is never spoken"
row "Pairing and sign in codes" +x note="not words"
row "Cron and time fields" +x note="not words"
row "The code editor" +x note="not words"
after "Everything else"
row "Names, searches, notes, feedback" +hi note="a mic on each"The check that keeps it
A rule nobody checks drifts. On the web, a check reads every text field and fails the build if one has neither a mic nor a place on that list. A new field cannot slip past it.
Read the strip on the web page, and the value it came from.