Where the design community meets.
Thanks for the question. It's true that Adobe has traditionally not been afraid to let different product teams handle interactions like a color picker in different ways. In some cases this is due to tradition within the individual product and in some cases it's because a new product might want to do something in a way they have found optimal for their particular user base. But that can, as you point out, be frustrating at times for users of multiple products. It's a balance.
With new apps, we're taking the opportunity to have fresh conversations amongst all of our designers, product managers, and users about the best path forward. You can see this in the new app frame that products like Lightroom CC and Premiere Rush are using, and in the upcoming Photoshop for iPad. It's funny that you mention color pickers, because that's a specific pattern that has been given a lot of attention. Font pickers, too.
It's likely that as we learn from these new common patterns, you'll see some of that make it's way into the existing flagship apps. But we've found in talking to our existing users that there's a careful balance to be made between making big unilateral changes and keeping the UI that they're familiar with and use to do their jobs. One seemingly small change, even for the better, can result in tons of productivity lost in the creative industry.
Thanks for the answer - but I wonder if it is ultimately a problem in the target audiences. Someone who is using Animate to animate a little animation to be published as a video actually can invest the time it needs to learn completely different interactions to similar UI Problems, because they need to learn it anyway. But for me, I just want to animate an SVG and export it on a web project - and this is basically impossible for me. I ended up animating it by hand with CSS, because the way Animate works and thinks is so entirely different from the way that animations on the web work, that it would have taken me a considerable amount of time just to learn the basic concepts. As a UI engineer, I just don't have the time for this.
Another example is defining Colors via libraries. I do my UI Design in Sketch, but all our Print Design and Images for Social Media or other types of Content are created by another department in photoshop, illustrator and indesign. So we have created a library for the colors. Turns out, nobody truly thought of how you handle Swatches in Libraries that have slightly varying RGB & CMYK / Pantone Variants. There is no 1:1 conversion from rgb to cmyk and usually designers define specific colors for those versions. Why is there no option to define different color space versions for swatches in libraries? The fact that this has not been brought up apparently by other people, also seems to me that multidisciplinary professionals have started to move on from the creative cloud to other solutions. And it also seems that adobe does not care that much about it - many efforts, and imho Spectrum too, try firstly to appeal to the non-professional target audience, which sometimes means stripping complexity, or flattening the initial learning curve by hiding more complex features in old menus and deep interactions or keyboard shortcuts.
Is there a conflict in priorities, especially when it comes to Spectrum, in setting priorities to support very different target audiences?
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.