Skip to main content

PUBLIC ROADMAP

Direction, without pretending every idea is a promise.

Shipped work is factual. Building work is active but can change. Exploring work is a design question, not a release commitment.

Dates and scope can move as Microsoft Store certification, security review, user feedback, and real Windows compatibility findings change priorities.
Now · July 2026Shipped

Gaming stability and honest telemetry

The current release cycle is focused on reliable focus handoff, compact chrome, real PresentMon FPS capture, GPU adapter identity, and a configurable detached HUD.

  • View, Interact, and Focus modes
  • Real local game FPS and process telemetry
  • Left and right HUD placement
  • No synthetic performance values
Next · Q3 2026Building

Public launch and licensing connection

Connect the existing entitlement model to the final Microsoft Store launch path while keeping account, device, and download controls understandable.

  • Microsoft Store certification
  • Final Free and Pro entitlement mapping
  • Purchase restoration and support flows
  • Launch documentation and onboarding
Later · Q4 2026Exploring

Portable workspace continuity

Explore optional, privacy-conscious ways to move user-created templates and settings between trusted devices without turning local browser data into cloud sync.

  • Selective template sync
  • Explicit encryption and recovery design
  • Conflict-safe import and export
  • No silent browser-session upload
Beyond · 2027Exploring

A broader desktop command surface

Study deeper Windows integrations and extension points only where they preserve Side Whisper’s compact, predictable, low-interruption character.

  • More local automation hooks
  • Additional accessibility controls
  • Carefully scoped integrations
  • Public roadmap updates before commitment

ROADMAP RULES

Stability, privacy, and truthfulness outrank novelty.

Ship the foundation first

Windowing, typing, recovery, packaging, and security work comes before decorative breadth.

Do not invent proof

Telemetry, performance, compatibility, and plan claims stay bounded by what is actually implemented and verified.

Preserve user control

Sync, automation, and AI-adjacent features must remain explicit, scoped, reversible, and privacy-conscious.

Document material changes

The roadmap, changelog, docs, privacy policy, and terms should move with the product.