I think the emulating/use native problem for the keyboard is a really tricky design problem to solve. Currently the 'Apple recommended' way is to use an inputAccessoryView which is essentially a bar above the native keyboard. There could be a more elegant solution. However, as you say, the broad spectrum of inputs for different locales makes this a tricky issue.