FluentView evidence
Fluent field guide

Control Windows with less effort.

Start with the question that matters, then inspect the evidence behind the answer.

Read the short answer
By Jason Matthew SuhariReviewed July 16, 20265 minute overview
Short answer

What will you find here?

The Fluent guide library explains what voice, text, and optional gaze can do on Windows, where the current preview stops, how data moves, and how Fluent is evaluated. Each guide distinguishes implemented behavior from planned or measured outcomes and links to primary research or official platform documentation where those sources apply.

Six focused answers

Find the guide for your decision.

01
Windows voice control

Voice control for Windows, with intent kept visible.

Yes, in preview. Fluent can accept a spoken request, transcribe the audio on the Windows device, send the resulting text to a user-configured hosted planner, and run Windows UI Automation tools. The current app exposes progress and cancellation, but it is not yet a finished assistive technology product. The published research and privacy pages document unresolved release and safety gates.

02
Voice plus optional gaze

Voice names the intent. Gaze clarifies the target.

Voice or text expresses the requested outcome. Optional gaze supplies recent target context for references such as "that file" or "this button." Fluent resolves a stable fixation locally to a semantic Windows accessibility element and sends structured target metadata with the submitted command. Looking never clicks, selects, or runs an action by itself.

03
Hands-free Windows use

Hands-free control works better as a layered system.

Fluent is being built to reduce keyboard and mouse use through voice requests, optional gaze context, and Windows automation. A spoken command can start a task and voice can cancel, but the current preview is not yet a complete no-hands system. Setup, provider credentials, some confirmation paths, gaze recovery, and reliable installed workflows still require keyboard, pointer, or developer assistance.

04
Product comparison

Fluent or Windows Voice Access? Start with the job.

Choose Windows Voice Access when you need a supported, built-in Windows 11 tool for direct voice navigation, dictation, named controls, number overlays, and grid-based pointer movement. Evaluate Fluent only when you specifically want a developer preview that turns natural requests into multi-step Windows automation, can add optional gaze target context, and exposes progress with published limits. Many users may keep Voice Access as the dependable baseline while testing Fluent separately.

05
Privacy and safety

Know what stays local, what leaves, and what can act.

Fluent keeps raw speech audio on the Windows device for local transcription and does not persist raw gaze samples. It sends the resulting text request and relevant structured context to the hosted planning provider configured by the user. Fluent has cancellation, action visualization, safety classification, and confirmation mechanisms, but its published research record identifies unresolved consequence-approval and product-hardening gaps. It should be treated as preview software, not a finished safety guarantee.

06
Research and evidence

Measure the whole task. Publish the failures too.

The current preview implements local command transcription, typed fallback, optional semantic gaze context, Windows automation, visible progress, and cancellation. Prior human-computer interaction research supports testing complementary speech and pointing signals. Fluent does not yet have public installed-product benchmark or accessibility beta results, so this page publishes the protocol and release thresholds that future claims must meet. The private implementation is not offered as independently inspectable evidence.

Choose the shortest path to your answer

Use the Windows voice control guide for the broad product category. Use the voice and gaze guide when target selection is the hard part. Use the hands-free guide when you are planning a practical setup around fatigue, pain, tremor, injury, or another access need.

The comparison, privacy, and research pages are for deeper evaluation. They explain when the built-in Windows option is stronger, what stays on the device, what reaches a hosted planner, and which outcomes Fluent has not measured yet.

  • Windows voice control: how Fluent turns a request into Windows UI Automation actions.
  • Voice and gaze control: why gaze supplies context but never acts by itself.
  • Hands-free computer control: a practical layered setup with voice, text, keyboard, and optional gaze.
  • Fluent versus Windows Voice Access: a direct comparison without declaring a universal winner.
  • Privacy and safety: an input-by-input data flow and a candid preview risk register.
  • Research: the published protocol, current evidence, and scorecard that will hold future claims accountable.

Read claims in three confidence levels

Implemented means the behavior is present in the current preview and described in the product disclosure. Planned means it is a release target, not a dependable current claim. Measured means a named protocol has produced repeatable results.

Fluent is still a preview. That distinction matters. A polished description should never erase a missing first-run flow, a safety gap, an incomplete gaze recovery state, or the need for installed-app testing.

Written from the current product record

These guides are maintained by Fluent creator Jason Matthew Suhari. Product behavior is checked against the current implementation and documented limits. External comparisons use first-party platform documentation. Research claims point to the original publication whenever possible.

If a guide and the installed preview disagree, installed behavior wins. The page should then be corrected and its reviewed date advanced.

Direct answers

Questions people ask before trying Fluent.

Is Fluent available as a finished Windows app?
No. Fluent is a preview for developers and early testers. The research and privacy pages list the release gates and safety limits that remain.
Are these guides medical or occupational advice?
No. They explain software behavior and evaluation choices. Individual access needs may require an assistive technology specialist or clinician.
Can readers verify the product claims?
Partly. Current behavior and limits are disclosed on this site. External comparison claims link to official Microsoft documentation, and research claims link to primary publications. The private implementation is not presented as independently inspectable evidence.
Check the record

Sources and product disclosures.

  1. Fluent privacy and safety disclosureCurrent data boundaries and known safety gaps.
  2. Fluent research methodEvidence status, benchmark protocol, and release thresholds.
  3. Fluent guide libraryCurrent product explanations and comparison pages.
Written and maintained byJason Matthew Suhari

Creator of Fluent. Product claims are reviewed against the current implementation and published limits.

GitHub profile
Keep reading
01Windows voice control

Voice control for Windows, with intent kept visible.

02Privacy and safety

Know what stays local, what leaves, and what can act.

03Research and evidence

Measure the whole task. Publish the failures too.

Inspect before you trust

Judge Fluent by the evidence.

Read the method, inspect the limits, and evaluate the current preview against published thresholds.

Read the research method