In many web applications the content retrieved by an end-user is not specifically adapted to the mobile device. In such cases the rendering can be done on the client side in the mobile browser or on the network side by a content-rendering proxy.
 

The drawback with so-called automatic rendering of web content is that the service and content providers lack "look-and-feel" control over what is presented. It is not optimized for mobile applications or for creating a rich end-user experience.

An alternative and better approach is to adapt the content to the mobile device directly on the server side. This includes selecting appropriate markup language and tailoring the content to the capabilities of the device. The content can be coupled to static pages, or it can be a dynamic page, provided by a Java EE container (or by technologies not covered here, such as ASP.NET and PHP).