Hi Ian:
Well, you know that someone will implement voice recognition on an EFB someday. (Cars already have it.) Might as well be iFly.
As for understanding Fixes, I understand. A lot of times in flight I don't understand what ATC is saying either. So I'll most often just repeat back phonetically what I hear and then find it on the chart. (And if I can't figure it out, I'll ask ATC to spell it out.)
Since we're brainstorming, the logic could do this: offer a list of fixes within 20 miles that sound like what you said. Or, since understanding phonetics is probably too hard for tablets (I just spoke "FIXEM" into my smart phone and google thought I said "Fix Some"), there would be the requirement that you spell out the FIX using ICAO alphabet. That makes voice recognition easier. (Although my phone got the FIX part right - so iFly could present a list of intersections starting with FIX.) iFly could use its already implemented logic to give you a short list of fixes, like it already does in the FP page. You say "iFly, choose two." (Like my Dragon Natural Speaking.)