[1]: https://plus.google.com/100275307499530023476/posts/ViCME1bb...
Hackborn starts with a stick ("I suspect we are going to need to start doing things to prevent you from impacting our app ecosystem") and then shows just a tiny glimmer of carrot ("Doing this correctly, without impacting our app developers... I also think it is something that needs to be done at the mainline platform level...")
So who knows what to make of that. My main reason for hope is that it's just so unusual for Google to speak out that way. All kinds of bizarre things get added to ROMs and they just ignore it. Then this comes and the Google engineers go bananas. It has to mean (or at least, I think it has to mean) that they have some plans around it, and they really don't want something incompatible coming out and becoming a defacto API ahead of that.
One PCs you have right click and double click, which are both replaced with long click. Using PC design interfaces on mobile will usually work (2 becomes 1). But the reverse fails because 1 cannot become 2.
I think it's a bigger jump than just a little optimization. Consider:
I would love for Google to address these things but they haven't shown any sign of it. The fact that they went out of their way to kill multi-windowing in CyanogenMod is interesting ... and the fact that the CM team complied without a whimper suggests that something may happen on that front, but I might be hoping more than really optimistic.