Let’s talk about gradients

The author released an editor in 2017 that flips the conventional gradient model used by Adobe Illustrator, Figma, Sketch and similar apps. Instead of limiting users to the four standard gradient types—linear, radial, angular and diamond—defined by SVG or CSS, the new UI ties colour stops directly to the drawn geometry, letting designers drag, nudge or type exact percentage values for each stop. The implementation required no novel algorithms; the breakthrough lies in refusing to let export specifications dictate the UI, thereby exposing a design‑tool ceiling that has gone unchallenged for years.

This redesign arrives at a moment when design software is increasingly judged against AI‑driven generators that can produce sophisticated colour transitions with a single prompt. Those generators expose the rigidity of current gradient panels, which are essentially visual representations of file‑format syntax. By treating gradients as an editable property of the artwork itself, the 2017 editor anticipates a broader shift toward toolkits that prioritize creative intent over format compliance—a shift that could pressure incumbents to add more expressive, data‑rich controls or risk being bypassed by prompt‑based workflows.

If the approach gains traction, we may see a split between legacy tools that cling to spec‑driven panels and next‑gen editors that expose granular, numeric controls for every visual attribute. The main risk is fragmentation: without a common export standard for these richer gradients, designers could face interoperability headaches when moving assets between platforms. Watch for plugin ecosystems or API extensions that bridge the new editor’s model with existing formats, and for major vendors to either adopt similar precision‑stop interfaces or double down on their current, less flexible paradigms.