I could see a limited use in graphics applications, as the keyboard becomes largely useless (or rather not useless, but less intuitive). However, even then a specialized hardware controller for Photoshop or Illustrator (or both - as most of the Adobe products have similar tools in similar locations) would be a more attractive - and cost effective - application. The only application where this interface would be both more intuitive and more cost-effective would be on the desk of the artist/sound engineer/videographer/programmer - and while some of us may do all of these tasks (actually, I do), we do some more than others, so the importance of a specialized interface for each and every task is not very important at all.
In my case, I do a lot of different tasks that could make use of a lot of different inferfaces, but I only really care about audio editing (my main hobby) and programming/administration (my livelyhood). I do some graphic design and gaming and countless other activities, but I don't do them often enough or care about them enough to find the keyboard overly-inefficient. I can put up with the general-purpose interface (although if I had a million dollars I would probably buy a tablet
).
On another note, in my music creation - I have about 4 pc interfaces that I use at any one time (mixer, my MPC, keyboard, and mixing interface). The only interface that would make a somewhat-usable transition to this product would be the MPC - but even then I don't know if it can take in velocity data. My point is that most specialized applications require multiple interfaces, not just one.
