Hi everyone. I've been deep in a side project to unify my team's productivity tools, and I wanted to share a visual component I built for it using Recraft.
The goal was to create a custom, cohesive set of app icons for our internal productivity "suite" – a collection of tools we've connected via APIs. We use a core CRM, a marketing automation platform, a custom dashboard, and a few other services. Having mismatched icons in our shared bookmarks and documentation was a minor but constant source of friction. I used Recraft to generate a full set in a consistent style.
Here’s a quick breakdown of the process:
* I started with a base style prompt for a "modern, flat, slightly rounded icon with a soft gradient, on a neutral background."
* For each tool, I refined the prompt with a key color and a simple metaphor (e.g., "a linked chain for Zapier," "a branching path for our workflow automator").
* The batch generation and style consistency features were a huge time-saver. I could generate 3-4 variants for each concept and pick the best one.
The final set looks professional and unified. It’s a small touch, but it makes our internal wiki and onboarding docs feel much more polished. It also got me thinking: has anyone else used Recraft for similar functional design work within their tech stack, rather than just marketing assets? I'm curious if you've found it useful for creating diagrams, simple UI mockups, or other internal system documentation.
That's a clever way to reduce cognitive load. We enforce icon consistency in our runbooks for the same reason. When you're paged at 3 AM and scrambling, visual recognition beats reading labels.
Do you version control the icon set? We had an incident because someone updated a Grafana dashboard icon and broke our script that scrapes panel IDs, which was keyed off the old favicon hash.
Good side project.
Batch generation and style consistency sound great in theory. Did you check the licensing terms for AI-generated assets on Recraft's site? I've seen clauses that grant the vendor broad rights to anything you create on their platform. Using it for internal corporate branding could be a legal headache later if they decide your "cohesive set" belongs to them.
Also, how's the long-term maintenance? If Recraft changes their model or goes under, you're stuck with static PNGs. Try adding a new tool to the suite in six months and matching the style exactly. Unless you documented the exact prompts and seed values, reproducing that look is going to be a pain.
Vendor claims are hypotheses, not facts.