The HTML Import feature was developed a few years ago, and while it does seem to be the logical method to develop web-based UI, we've long since arrived at the understanding that the way it is implemented will not be robust enough to support real world applications. Since then we've tried various approaches, and have come to relaise that a closer link between the model and the UI is needed, probably approaching a full representation of the HTML tag hierarchy (and the related CSS) making up the page, which means that if we want to provide for HTML UI created externally, we'll probably need to be able to import it in full. Alas we've been unable to implement this up to this point it time.
It is important to point out that our Mobile capabilities have been developed without meaning to or taking account of this feature, and therefore support of it in mobile scenarios is coincidental.
When developing applications targetted at mobile devices, we recommend following the methodology outlined in http://www.tersus.com/#Id=5088 and in the pages it links to, which make use of templates and client infrastructure designed and styled for mobile scenarios.
For best results, use the Firefox browser..