I would love to hear how others handle clear version labeling and fidelity leveling in their Figma screens / components.

I’d wondered whether it would make sense to have any property types that could be automatically applied to components, configured at the file or organization level. Whether these are fully open ended, or perhaps more realistically ‘tied’ to concepts like “Version” or “Fidelity,” this has been something we have done manually ourselves to track our components.

Example “Fidelity Type” Property values: Low, Medium, High

We have found ourselves sometimes turning low fidelity screens into components to explore layouts, or even just to have a lower fidelity option to share out (thanks luminosity!) even as we are working on medium or high fidelity concepts. At times this has meant taking an existing component and adding a “Fidelity” property to start tinkering splitting out the next phase of iteration even if some project screens still live in low fidelity land. Whatever your team’s process, I wondered if it would be helpful to have automatically applied / defaulted fidelity values to amplify / echo team build habits.

Example Version Type Properties: v1, v1.1, or even v1 - Mary, v1.1 - Tom, etc.

This type property might benefit from default naming / numbering scheme, but could also perhaps include the designer / author of a version, letting you ask design team members to explore variants via components and have ‘versions’ or alternatives tied to a known team naming convention or even a personal avatar.

It seems like the addition of these types of structured properties could become cumbersome or the source of yet additional complexity. At the same time it seems versions / fideelity are two example of common enough concepts that them being structured / organized for you might help power some interesting workflow or process views, showing how components might evolve or improve over time, auto-pruning old screen versions to reduce file size, etc.

Curious if anyone has thoughts on this, alternate ways to support this (besides manual property curation / definition for each component). Or does this belong in plugin-land?