On a Series 40 phone, if I use MIDlet.platformRequest to dial a phone number with some post dial DTMF digits, I get a confirmation dialog (which is annoying but not unexpected) and then the phone dials the number. After dialling, the user is returned to the MIDlet UI and sees my "call in progress" screen.
On a Series 60 phone, I get an almost comical cascade of confirmation dialogs which (as far as our application is concerned) renders this feature unusable. It first asks if I want to dial the number, then it asks if I want to send the DTMF digits, finally it asks what kind of call do I want to make - Voice, Video or Internet? Whilst I appreciate the marvellous flexibility and choice offered by these dialogs, my end users do not, and won't use my application! In fact, the user experience is even worse than this, because about half a second after the first "dial?" dialog has appeared, the screen flicks back to my MIDlet with its "call in progress" screen. The dial confirmation loses focus. To get focus back, I have to hold down the menu key to get the task list up, and then switch to the WAP browser - there are actually two instances of the WAP browser running.
Did anyone try this facility out before it was put into a phone? Exactly which target end users are the ones who like their midlets to be able to dial phone numbers, not send the required DTMF tones, and try to do this using Voip, even though it hasn't been configured on this particular handset?
Coping with this sort of experience would test the patience of many power users I suspect!