One of the things I really hate currently is taking the current fads in interface design and applying them in the not unlikely scenario that I'm driving with my iPod/iPhone docked. If I'm plugged in, with my phone in landscape orientation for more than a few moments (ie, to make selection of a choice of things easier in the orientation layout), even if I'm not driving DON'T EVER ASK ME ANYTHING OR POP UP OR INTERFERE WITH ME AT ALL! I'm in a context where it is reasonable to assume I'm viewing something and don't want to be bothered.
You mention the shake interaction; I found out that Google Maps on iOS has this while driving and using it for navigating when something triggered it and in small text Maps pops up a "useful and helpful" explanation that I can report issues with the app by shaking the device. But then they took it one step further and made it a modal dialog with "OK"/"cancel" such that you have to read, process the info and successfully choose and execute one of two options. Did anyone at Google, at any point, think and articulate that perhaps having an easy to accidentally trigger interface was a bad idea and that perhaps the worst way to handle the fact that it was easy to accidentally trigger was to pop up a modal dialog box with small text and then proceed to force a user to use multiple higher level cognitive functions while the device's sensors indicate that, one could reasonably assume, they are in the middle of operating a vehicle at 75 MPH? Either they considered it and didn't care or they never considered in what context one might use their application. So they're either dumb or evil, take your pick.
That's the tip of the iceberg. I'm reasonably certain that the point of Google Maps when in GPS mode is to kill and maim as many as possible. It'd be one thing if they didn't have access to sensors that can give a very reasonable assumption as to the context in which the device is operating, but there's more than enough information to derive the context in which the phone is operating. GPS, power, Bluetooth, NFC, screen orientation, mic, etc. I cannot think of a situation in which I'm in a loud environment, Bluetooth connected to an audio device with remote controls, power connected, screen in landscape orientation, while moving at > 5 MPH, with a mapping application using GPS, in which it cannot be reasonably assume I'm driving. Yet, so many of these apps that only get used in that very context won't take that into consideration with regards to their interface. The only one I've ever seen get it right is a war-driving application. Feedback is large text in a dashboard mode in landscape orientation, or a different output in vertical orientation with configurable audio feedback at defined intervals. It never tries to ask you a question while its in use and the layout is such that you aren't likely to need to interact outside of one large start/stop button and changing the device's orientation.