Brand guide
Custom JUCE and C++ Integration
Use the JUCE package when possible, or integrate directly with the SoundSync HTTP licensing API from a custom C++ client.
SoundSync
Branding reaches plugin customer screens
HISE and JUCE package screens reuse product identity, color, logo, support, and store context so activation and ownership feel connected to the developer brand.
SoundSync
Store branding follows the in-app catalog
The JUCE Store catalog shows how branded customer-facing product browsing can appear inside the package experience after setup.
SoundSync
Brand field matrix
These values are reused across SoundSync surfaces, with generated packages refreshed through regeneration when static values are embedded.
| Field | Where it appears | Update behavior |
|---|---|---|
| Store name and tagline | Storefront, marketplace, checkout, customer library, email, package UI. | Dynamic on web surfaces; regenerate packages for embedded values. |
| Logos and fallback initials | Storefront, Website Builder, marketplace, HISE/JUCE package UI, support surfaces. | Upload/replace in Brand Manager; regenerate generated package assets when needed. |
| Primary, secondary, tertiary colors | Website Builder, storefront, checkout accents, customer library, HISE/JUCE components, marketing email. | Dynamic where platform branding is read; package snapshots require regeneration. |
| Support email and URL | Product pages, activation UI, My Products, customer library, receipts/support pages. | Keep customer-facing support routes current before publishing. |
| Custom domain and email domain | Hosted storefront, branded links, sending identity, tracking, customer trust. | Requires DNS verification and SoundSync SSL certificate readiness for web domains. |
Package regeneration rule
When a generated HISE or JUCE package contains static brand config, regenerate it after major logo, color, support, domain, or product identity changes. Do not rely on dynamic propagation where a package uses generated values.