My wife recently got a Samsung Galaxy tablet and there’s been a bit of a learning curve for both of us. I haven’t had a lot of experience with tablets — and I probably won’t get much experience with this one because my wife has done a good job of keeping it away from me. Understandable, because for one, it is hers, and I also tend to monopolize the gadgets in our house. So, with limited experience AND limited access, when I have been able to use it, there have been some hiccups — mainly just trying to figure out how to make things work and where to go to get certain apps to run. I’m picking it up, though.
As for giving directions, I usually tell someone to Google it. Seriously. It’s not that I don’t know what streets someone should take, I just don’t remember specific names. I know what the scenery looks like, but that’s not always the best way to direct someone. Even streets I should know, like in my hometown, someone will say the street name and I’ll have to take a minute to visualize where they’re talking about. “Oh, yeah, that’s where you turn left!”
I suppose the lesson then for developers is that everyone handles interactivity and directions in different ways. One person’s intuition for how things should work is nothing like someone else’s intuition. So it’s critical for developers to consider not only what they think a device should do, but what the average Joe would expect from a device.