Ok, sounds like there are a few reasons not to make mobile available on desktop, yet. Although, it's good to hear that it may be considered in the future. I'm not sure what backend code issue(s) you will run into, other then absolute urls for example. Not sure if these ideas have been considered as workarounds, and I understand there are reasons they may not be possible. 1) .htaccess rewrites to spoof /mobile/ folder to the root folder and have that checked at the same time you check the useragent to determine if they need mobile site 2) using a mobile.tip.it/ subdomain and have that checked at the same time you check the useragent to determine if they need mobile site Again, I am sure there are reasons these may not work, but just wanted to throw the idea(s) out there. We're already serving the mobile site based solely on the useragent - which is why so many people suggested to the OP that the best way to access the mobile site from his desktop was to spoof his useragent. Using the subdomain would be ideal, but that's what peter is saying is the difficulty: it may not be possible to properly share the framework we use between multiple sub-domains.