Files
VoiceStudio/docs/branding.md
T
Palash Debnath 04410a458d Release VoiceStudio 5.0.0 (#1487)
Complete the VoiceStudio identity, release documentation, assets, version mirrors, and safe cross-platform development startup.
2026-08-11 04:05:45 +00:00

2.2 KiB
Raw Blame History

VoiceStudio brand

VoiceStudio uses a waveform-and-spark mark. The waveform identifies audio; the spark identifies creation. The product voice is clear, calm, and direct.

Assets

Surface Source
Primary vector mark docs/logo.svg
README mark docs/logo.png and docs/logo-256.png
Browser icon frontend/public/favicon.svg
In-app mark frontend/src/components/brand/VoiceStudioMark.jsx
Desktop/platform icons frontend/src-tauri/icons/

Regenerate every desktop icon from the canonical vector after changing the mark:

bun run --cwd frontend tauri icon ../docs/logo.svg

Do not redraw the waveform per screen. Use VoiceStudioMark in React and the canonical SVG elsewhere so the silhouette stays recognizable at 16512 px.

Palette

Role Color
Voice rose #F47FA3
Soft highlight #FFD0DB
Creative amber #F7AE73
Spark #FFE5B5
Plum tile #211B2B#120F18

The mark may render in one color inside app chrome. Keep the waveform and spark together; do not put text inside the icon or add another enclosing ring.

Name and copy

  • Product name: VoiceStudio—one word, capital V and S.
  • Voice: concise, professional, warm, and direct.
  • Promise: local-first creation without a subscription or usage meter.
  • Avoid absolute privacy claims: network-backed engines, downloads, analytics, and cloud integrations are explicit opt-ins, not nonexistent.
  • Attribute the bundled default model as k2-fsa/OmniVoice where model lineage matters. OmniVoice is an upstream model/runtime name, not the product name.

Compatibility names

The rebrand must not break existing installations. Keep these identifiers until a separately tested migration exists:

  • omnivoice Python imports and package name
  • omnivoice-studio binary/package and published container coordinates
  • OMNIVOICE_* environment variables and X-OmniVoice-* API headers
  • existing OmniVoice data/cache directories and uninstall aliases
  • upstream repositories, model IDs, classes, and engine IDs

Visible copy can explain those compatibility names, but must not silently rename them on disk or over the wire.