Hi Simon,
Yes totally agree with you ... implementation of "bleeding" edge applications (then in 2004) often leads to much bloodletting... and thats No Good (TM). Thanks for reminding me to test it with a Chinese handphone!
However, I noticed that the wireless module now is using WAP 2.0 specifications (the WAP page cannot be viewed with a WAP 1.x browser). How that translates to a more consistent / stable implementation of WAP protocol by the telcos remains to be seen.
As of now, I have tested the WAP pages on some clamshell Sony Ericsson phones and they *suck*. Don't know if it is a browser issue or layout issue or form factor issue, but the words are too small and text entry was really painful (you have to switch out to another text entry screen to enter the user id and password and then switch back to login - *terrible*)
I have not tested the pages on a Nokia phone as apparently all the phones now come with HTML browser and when you login to the URL, you see the HTML login page for OTM - and thats No Good (TM). So I have to find a Nokia phone with a WAP 2.0 browser. And surprisingly its not that easy
Anyway, I still have many doubts about the feasibilitiy of such an implementation - but thats what POC's are for
...
I hope to be able to come up with some scenarios where the implementation works well and will share it once I have completed the POC.