phermi
03-18-2008, 01:56 AM
Hello,
New user here ... so forgive me if my topics doesn't fit here. I am looking for guidance and enlightnement. Hopefully you can point me in the right directiosn .....
Does anyone know how to contact the development team for Windows Mobile 6 or how can develop a smar "phone" application?
Weird question, ah?
Well we just need to provide feedback to them in regards of the phone application or get someone to develope a better one. My 6 years old could have done a much better job.
In essence, they forget that the things running WM6 are phones and therefore phone related activities must have the maximum priority, flexibility and power.
Let's put in here one of our main problems: We all use Exchange and therefore there are imposed security measures like locking the phone. No too much of a problem per se.
Now, our VoIP PBX allows us to perform what we call selective answering: when a call is transferred to our mobiles phones, the caller is identified and put on hold and we can hear his name. Then we can punch one key to accept the call, another to reject, another to playback a voice message and another to send the caller to voice mail.
Here is the nightmare: The call come in the WM6 device that someone forgot is a phone. Well in order to access the phone application, you have to unlock it first (after you have located it and have it in your hand, very nice process if you are driving). This implies a delay measurable in seconds. Then you get to the phone application, but there is no keypad so you need to click with your huge fingers on "Keypad" to finally be able to punch the desired key. This all takes time .. time that (1) the caller is waiting and (2) the VoIP PBX is waiting for user input. Most of the times, users can not get to their callers (and please do not tell me to increase the PBX waiting time).
The reasonable thing to do here is to accept the fact that this device is a phone. Therefore an incoming call MUST be passed straight through to the phone application with the keypad fully expanded. Any attempt to access ANY OTHER function of the phone will still require the device to be unlocked first, including obviously accessing contacts during a call. This behavior can be either a user-friendly option or a hack to the registry.
Another smart thing about the phone application is that if the "Keypad" is expanded, then there is no way to access your contacts from that screen. Who most likely you want to call when you are in phone mode? Some of your contacts, of course.
That is it ... for what is worth ...
This is affecting our 150+ Users of WM6 and I am sure we are not alone.
Any info will be highly appreciated.
New user here ... so forgive me if my topics doesn't fit here. I am looking for guidance and enlightnement. Hopefully you can point me in the right directiosn .....
Does anyone know how to contact the development team for Windows Mobile 6 or how can develop a smar "phone" application?
Weird question, ah?
Well we just need to provide feedback to them in regards of the phone application or get someone to develope a better one. My 6 years old could have done a much better job.
In essence, they forget that the things running WM6 are phones and therefore phone related activities must have the maximum priority, flexibility and power.
Let's put in here one of our main problems: We all use Exchange and therefore there are imposed security measures like locking the phone. No too much of a problem per se.
Now, our VoIP PBX allows us to perform what we call selective answering: when a call is transferred to our mobiles phones, the caller is identified and put on hold and we can hear his name. Then we can punch one key to accept the call, another to reject, another to playback a voice message and another to send the caller to voice mail.
Here is the nightmare: The call come in the WM6 device that someone forgot is a phone. Well in order to access the phone application, you have to unlock it first (after you have located it and have it in your hand, very nice process if you are driving). This implies a delay measurable in seconds. Then you get to the phone application, but there is no keypad so you need to click with your huge fingers on "Keypad" to finally be able to punch the desired key. This all takes time .. time that (1) the caller is waiting and (2) the VoIP PBX is waiting for user input. Most of the times, users can not get to their callers (and please do not tell me to increase the PBX waiting time).
The reasonable thing to do here is to accept the fact that this device is a phone. Therefore an incoming call MUST be passed straight through to the phone application with the keypad fully expanded. Any attempt to access ANY OTHER function of the phone will still require the device to be unlocked first, including obviously accessing contacts during a call. This behavior can be either a user-friendly option or a hack to the registry.
Another smart thing about the phone application is that if the "Keypad" is expanded, then there is no way to access your contacts from that screen. Who most likely you want to call when you are in phone mode? Some of your contacts, of course.
That is it ... for what is worth ...
This is affecting our 150+ Users of WM6 and I am sure we are not alone.
Any info will be highly appreciated.