Unfortunately, the conversion from XML or HTML to WML is far from automatic. With nearly all these third-party solutions, the XML or HTML content must be created from the ground up and adhere to strict rules and templates, often in conjunction with SDKs and tools provided by the vendor. This approach is highly vulnerable to changes such as new page layouts. With XML, application developers can use specific tags to create mobile content that the middleware can interpret in an unambiguous, consistent fashion. The middleware can perform other functions as well, such as delivering mobile content using transport protocols better suited to wireless.
Application developers can deploy their applications on existing Web platforms.
The architecture also allows the middleware platform to deliver optimized content to the user with the most appropriate protocols for the connection. Many of these ASPs are new, and their long-term viability is unproven. In fact, many wireless middleware companies have come and gone over the past five years. Increasingly, major software vendors are adding capabilities to their Web and database platforms to support mobile formats. This could eventually obviate third-party solutions, though such solutions are likely to have broader network and device support for quite some time.