iPhone voice drafts: Dictation, Notes or Yihu?

Choose by task, not by the label “voice app”: use keyboard Dictation in a trusted editor, collect thoughts in Notes before choosing an Agent destination, or evaluate Yihu's native transcription and guarded draft handoff for your own web workbench. This compares documented boundaries, not untested accuracy, duration, speed or standalone Watch approval.

Choose a path for the task in front of you

Already in a trusted, editable workbench field that does not auto-submit: keyboard Dictation may avoid a separate handoff. Confirm the host's draft/submission rules; keyboard input is not workbench compatibility certification.
Capturing a thought before choosing an Agent destination: dictate into Notes, then explicitly choose a later handoff. Check the note account and sync policy; Notes is not automatically local-only storage.
Already own a trusted HTTPS workbench and want native local models plus target-checked draft delivery: evaluate Yihu. It is a source release requiring your service, signing and models; it does not host Agents or certify arbitrary workbench compatibility.

Documented boundaries across three paths

Swipe to read all columns. Keyboard users can focus the table and use the arrow keys.

Documented boundaries across three paths
Dimension	Keyboard Dictation → editor	Dictation → Notes → manual handoff	Yihu native speech → your workbench
Recognition location	Apple says Keyboard Settings indicates on-device processing; otherwise dictated content is sent to a server. Do not label every device/language fully on-device. [A1][A2]	This path means keyboard Dictation into a note, not a separate review of Apple's recording transcription. Recognition follows Dictation settings; check the note account separately. [A1][A2][A3]	Compatible Qwen3 ASR models run on the phone after separate download and verification. Downloads, browsing and later handoff are not offline guarantees. [Y1]
Automatic submission	Apple documents text entry at the selected insertion point. It does not guarantee whether a host automatically submits or saves that text. [A1]	This manual path first writes a note without calling an Agent send action. Later copy/share creates new copies and destination rules; other automations are outside this comparison. [A3]	Short speech may automatically attempt guarded insertion, but insertion code does not press Send. A page can save/sync drafts before message submission. [Y2a][Y2]
Workbench / page binding	The target is the user's selected text insertion point; that does not establish Yihu-style workbench/request-ID guards. [A1]	A note/account is not a binding to an Agent page. Recheck the workbench, page and draft editor before handoff.	Yihu checks trusted origin, page and request targets. Explicit voice-note insertion also checks the workbench/page captured when opening notes and the current interaction state. [Y2][Y3]
Host refusal	Arbitrary host refusal and auto-submit behavior is unverified. Keyboard editability alone does not make every editor safe.	Retain the note rather than forcing host integration. Paste only after confirming the destination permits drafts and does not auto-submit.	Explicit refusal or unknown responses do not fall through to a bypass. Failed safe delivery retains text; inspect the target instead of blindly inserting again. [Y2]
App Group staging / upload	Keyboard Dictation itself is not Yihu's App Group inbox; the receiving app/page controls subsequent processing.	Yihu staging applies only when you actually choose to share into Yihu. Other copy/share destinations have their own rules.	Yihu stages text, links and files first. A user handoff can reach a page draft or attachment control; an unsent message does not prove no file was uploaded. [Y4]
Models / permissions	Enable Dictation for the actual system version and check language availability and processing details in Keyboard Settings. This path does not require Yihu models. [A1][A2]	Check Dictation prerequisites and Notes account/sync settings. Removing an account does not erase notes from the internet account. [A3]	iOS 18+, your trusted HTTPS workbench, source build/own signing, compatible models and microphone permission. Do not bypass required verification when speaker models are missing. [Y1]

Keeping a note and handing it to a workbench are different

Apple documents that removing a Notes account from an iPhone can leave notes in the internet account and other configured devices. Check the selected account rather than treating “not sent” as a sync/backup check. [A3]

Yihu voice-note source retains local audio/transcripts and attempts backup exclusion. That is not this guide's proof of device backups, arbitrary long recordings or performance. Explicit handoff may create another copy or web-processing boundary. [Y3][Y3a]

Speaker matching is a convenience filter that can misidentify people, not account authentication or write authorization. Notifications, Live Activities, Watch and real replies have separate prerequisites; one draft handoff does not certify them. [Y1]

One synthetic walkthrough: stop at an unsent draft

This is a written process illustration, not a passed device test. This page does not call your microphone or workbench. Use an authorized empty draft/note, never real tasks or customer content.

Synthetic phrase: Draft a sample reading list; keep it as a draft, without sending or running it.

Swipe to read all columns. Keyboard users can focus the table and use the arrow keys.

One synthetic walkthrough: stop at an unsent draft
Step / action	Success signal	Otherwise
1. Choose the path and target before recording Confirm the service, page, editable draft and no-auto-submit rule. If the destination is unclear, choose Notes first and check its account. For Yihu, complete setup checks first.	The target is clear, or you intentionally stop in a controlled note without touching existing real tasks.	Do not record into an editor with unknown execution behavior; keep the separate capture path.
2. Capture only the synthetic phrase Use keyboard Dictation and stop it for the system path. For Yihu, use the recording entry point currently permitted by your version; short-speech completion may automatically attempt guarded insertion.	Text appears in a note, draft or native panel. Do not assume Yihu needs a second insertion click.	Stop at permission, model or host-refusal boundaries; do not disable checks or verification to bypass them.
3. Review text, destination and handoff boundaries If already inserted, inspect rather than insert again. Verify the destination before handing off a note. With Yihu sharing, distinguish App Group staging, attachment handoff and message submission.	Text is in the intended unsent draft or retained safely in a note/panel. No Send action is used for this illustration.	Inspect uncertainty at the destination. Do not force another editor after refusal or retry blindly.
4. End at the draft Stop after inspection. Do not invoke the Agent, test uploads or send real replies, and do not use this walkthrough as performance or feature certification.	The endpoint is an unsent draft or controlled note, not an executed task.	If the destination already performed sync/attachment processing, follow its actual rules; do not claim every copy was erased.

What this comparison does not establish

This is not feature-equivalence certification or a performance ranking. Apple columns use official documentation; Yihu columns use current source/README evidence. Check the actual system version, language, account, editor and service configuration.
No arbitrary long-recording, transcription-accuracy, speed, battery, push-delivery or independent Watch-approval claim is made. Merged source, website demos and static builds do not replace device/service acceptance.
Not pressing Send does not stop a web page processing drafts. On-device transcription is not a promise that all data stays on the phone. Do not bypass certificates, speaker checks, permissions or explicit host refusal.

Evidence and next steps

Setup checks and first draft · Data flow and speaker boundaries · Back to capabilities

Read mobile decisions, source freshness and phone confirmation boundaries