You overall idea is good terminator-jq, but it only works if you combine the two. Ho many 3+ key combos are there in complex applications? Having a developer pick the 3+ key combos of THEIR choosing will not benefit the user all that much. Being able to define your own, no matter what application, would be great. But now you are attempting to basically add scripting everywhere. Given that the tool bar will take a while to see wide customer usage(is this going to appear in all apple keyboards from now on???), this is adding a lot of complexity for saving a couple keystrokes.
I'm not seeing a ton of benefit, especially when I typically see professionals seeking exact colors/timeframes/etc... rather than a rough guess like the width of a finger on a 6 inch range.
Good points. As I said before, software companies need to use the touchbar to do things that would take 3-4 or more clicks to do with a mouse. What Apple showed for Safari, Photos and Mail was not good examples. All of those things can easily be done with 1 click. The Photoshop demo was without a doubt the best use of the touchbar.
As for custom buttons, obviously I don't know much about programming on Mac OS but I don't think it would be too hard to implement custom Touchbar keys. Take a look at MagicPrefs, it lets you use gestures to imitate key combinations on the trackpad. Also look as gaming mice, most of them have side buttons that can be assigned to emulate hotkeys. I don't see why the same thing couldn't be done with the touchbar.
For example, in Maya, there are quite a few hotkeys that are built into the program that require 3-4 key combinations. Not a big deal but it sure would be nice to touch 1 button instead of 3 or 4. So in this case, you could:
Step 1: You choose what application you'd like to create custom buttons for (for this example, I would select Maya)
Step 2: Choose to "create a new button" and hold down a key combination that is recognized in the program your using (example: Command, Shift, C). The program reads what buttons your holding down and saves the combo.
Step 3: You name the button (maybe assign a color too) and choose where it should be placed.
Step 4: When you open the application that you created buttons for, the touchbar will change to show your buttons. Pressing the buttons will be the equivalent of pressing the key combinations.
Since the touch button is simply emulating a key combination, no extra work needs to be done by the software company. As you said, it may take a while for the touchbar to see wide customer usage, therefore, some software companies may decide not to include touchbar support since it will not benefit very many customers. However, with custom buttons, you could in a way add touchbar support to any application (as long as the application has hotkeys).