Challenges in building wireless applications
How to write applications that have to work with both WML and HTML devices?
Handling sessions is a tricky task to do it in a portable and transparent way with all phones and WAP gateways
Browser implementations vary widely from vendor to vendor, or even from one version to another; supporting them all is a maintenance nightmare
How to display dynamic content such that the generated decks are not larger than the size limit?
Notes:
- UP.Browser phones support the access-key attribute for the anchor and a elements, which makes navigating through links faster. This attribute was introduced in WML 1.2, but there are many phones that still use WML 1.1, or even 1.0.
- When displaying a phone number on the screen, it would be nice to associate a button to a “call” action which, when pressed, makes a phone call.
- Attributes of certain elements are ignored by browsers: the title attribute of the card element is ignored by some phones.