Roadmap / Feature Requests

Problem Users cannot tell whether a palette actually fits their design until they apply it manually, which makes palette validation slow and speculative. Proposed Solution Add a quick simulation on the current selection. Detect colors in the selected page, illustration or component Remap each detected color to a palette color based on its luminance, computed client-side No semantics involved, purely a visual preview Acceptance Criteria [ ] Users can trigger a palette simulation on a selection [ ] Detected colors are remapped by luminance to palette colors [ ] Simulation runs client-side with no server call [ ] Original document colors can be restored after preview Use Case As a designer evaluating a palette, I want to see it applied to my existing design so that I can validate the direction before committing. Additional Context Exploratory hypothesis; precedes the more technical, template-based semantic simulation. Market Opportunity Shortens the path from palette creation to confident adoption, a strong hook for trial users.

Problem Exports assume sRGB only, so users on wide-gamut displays cannot output optimized color values for modern screens. Proposed Solution Make the target gamut an explicit palette setting. Support sRGB, Display P3 and Rec. 2020 Gamut stored per palette, not globally Default to sRGB for maximum compatibility Acceptance Criteria [ ] Gamut is selectable in palette settings, with sRGB as default [ ] Exported color values are converted to the selected gamut [ ] Existing palettes keep sRGB behavior after migration [ ] Selected gamut is stated in generated documentation and exports Use Case As a designer working on wide-gamut screens, I want to export in Display P3 so that my colors render as intended. Additional Context Applies to Figma, FigJam, Penpot, Sketch, Buzz, Framer. Market Opportunity Appeals to brand and media teams on high-end hardware, reinforcing the Pro tier value.