Hi all,



My company is looking to produce a mobile version of our current site. We've employed an external company to look at the options available to us and so far we have two options which I thought I'd ask you guys about.



1. Use the existing portal utilising a new mobile skin and new pages containing specificly written mobile modules.



Issues here appear that the payload is qutie large, almost 600kb for the initial load, and after caching, around 200kb per page. This seems extremely high. This was using the default minimal skin with no actual modules on the page. Our modules do use MS.Ajax though and DNN appears to be taking into account when generating the script resource even though no module is being used so just one of the files sent to the client is 300kb in size. Without our Member Services system and just the basic DNN install, the intial client download is 380kb, which still seems very high.



2. The second option (far more complicated), which is what the external company is suggesting is that a custom default page be created that reads from the DNN DB. All the config will be done in DNN but none of the actual display of the site. It will generate a menu on the fly based on what the customer of our product chooses. When a user selects a page, it will go into the DNN DB, get the page and then load it up. This page will be passed though a conversion app (that the external company said they will write) that will supply a stripped down page of just a very basic skin, .css, custom jQuery (not the full file) and our application modules. They believe they can then deliver a page to the client around 20kb or so.



The issue we have with this is that our current modules are written using Microsoft.Ajax components for the postbacks, and we're unsure if they can simply be converted in the way this compay is suggesting and still work in the same way, and also we're unsure if they can really supply the payload size they've suggested.



----



Does anyone else have a different suggestion other than these two approaches. One seems simpler but with a very high payload, the other seems like it would be very complicated but with a very small payload to the client.



If anyone has an app that they have written that does something similar to my requirements, I'd be very interested to hear, or of a company that has done similar work for you.



Any other advice regarding a duplication of a current site to a mobile site would be much appreciated.



Thanks



Nolan