Skip to content

feat: move the voice over control to the top of the composer and gate it in proudction - #184

Merged
Nhaaa4 merged 1 commit into
mainfrom
feat/voice-over-coming-soon
Oct 20, 2026
Merged

Nhaaa4 merged 1 commit into
mainfrom
feat/voice-over-coming-soon

Conversation

@Nhaaa4

@Nhaaa4 Nhaaa4 commented Oct 20, 2026

Copy link
Copy Markdown
Member

Summary

  • Moves the Voice over control to the top of the prompt box, next to the Brand DNA chip, and restyles it to match that chip (same font size, plain icon color, no On/Off in the label).
  • The control is now a dropdown with On, Off and Customize voice. Customize voice opens a short text field for a voice direction (for example "calm, warm female voice"), which is appended to the prompt as Voice over direction: ….
  • Production builds (VITE_DD_ENV is prod or production) don't show the dropdown. Clicking Voice over opens a "Coming soon" card, styled like the "We're still early" notice and rendered on document.body so it centers over the whole page.
  • Production never requests voice generation: tts is always sent as false and the voice direction isn't added to the prompt. This goes through a new shared helper, isVoiceOverReleased(), used by both the panel and App.svelte. Before this, the toggle defaulted to on, so production requests still asked for a voice over.
  • Also in this branch (already in the working tree before this work): the tts type additions in direct-ai.ts and generation-guidance.ts, and the "Untitled Motionly Project" to "Untitled Motify Project" rename.

Testing

  • npx svelte-check: 0 errors, 0 warnings.
  • npx vitest run src/ui/cloud/TiffyPanel.test.ts: 24 of 24 pass. This covers the On/Off/Customize dropdown, the production coming-soon card (opens, sits outside the composer, closes with "Got it"), and the no-toggle case for local projects.
  • Not run: the full npm test.
  • Not covered by a test: that tts is false in the generation request in production. I checked that by reading the code, and no other place in src/ sets tts.

Visual Evidence

  • N/A

Risk

  • Low. The change is mostly in the prompt composer UI.
  • In production, users can't turn voice over on. This is intended until voices ship.
  • The production check depends on VITE_DD_ENV being exactly prod or production. Any other value gets the full dropdown and can request a voice over.
  • Voice direction is only added to the prompt text. The backend takes only a tts on/off flag, so there's no real voice selection yet.
  • Developers whose local .env sets VITE_DD_ENV=prod see the coming-soon card and need dev to test the dropdown.

Checklist

  • I ran npm test.
  • I kept the change scoped and readable.
  • I updated docs for composition, preset, export, or public behavior changes. (No docs affected.)
  • I did not mutate imported assets or add hidden renderer state.

… it in production

The voice over switch is now a dropdown (On, Off, Customize voice) styled
like the Brand DNA chip. Production builds (VITE_DD_ENV prod) open a
coming-soon card instead and never request voice generation.
@vercel

vercel Bot commented Oct 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
motionly Ready Ready Preview Oct 20, 2026 2:22am UTC

@Nhaaa4
Nhaaa4 merged commit f4ac41f into main Oct 20, 2026
7 checks passed

This branch was successfully deployed

1 active deployment
Preview — 8ecd9565 Deployed Oct 20, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant