Home / Use cases
Made for people who ship brandsWhether you manage a brand, freelance across a dozen of them, or ship pixels to production — here's where Pocket CVI fits into a real working day.
A new campaign lands and three agencies are asking for “the exact brand colors.” Instead of digging through old PDFs, you open the brand kit, confirm the hex values, read your own usage notes — and the brand's official guidelines are linked right at the top of the sheet. One export later, everyone's working from the same file.
New client, existing brand. You point Collection from Website at their site and get the palette, logos, and webfonts before the kickoff call ends. You refine with the loupe, write your recommendations in the notes, and at project wrap hand over a generated design manual plus the kit as a single .pocketcvi file.
You're translating a design into code and need the button color that isn't in the spec. You pick it off the mockup, grab it as HEX or RGB with one click, and check the text-on-button contrast before it ever hits a pull request.
The rebrand is approved and now the client needs “the assets.” You package colors, logos, fonts, and your guidance notes into one collection, generate a brand-typeset design manual, and export the lot. They double-click, import, and have the entire identity — no zip of loose files, no missing font.
You're a one-person studio building on two Macs. You extract a base palette from your app icon, describe the vibe to the AI generator on your own key (or a local model), and iCloud keeps the collection — logos and fonts included — in sync so the colors you picked on the laptop are on the desktop by morning.
Readable is non-negotiable for your work. You build the palette, then test every foreground/background pair against WCAG-style contrast right in the app, and document the approved combinations in the collection's notes so nobody guesses later.
