Originally Posted by Disco181
I've been reading this thread with interest but I have to say I believe the problem is not as straightforward as these posts suggest. Surely it's necessary to take into consideration the content of the home / landing page (and other pages) when deciding on how to handle mobile visitors?
I agree entirely, but as things currently stand, mobile experiences are in almost all cases seriously held back in their functionality (not through lack of browser support but through false assumption on behalf of the developer). I therefore maintain the need to have both sites readily available for the end user - even if the method of providing that access is from one site to another. Too many designers dumb down their work because they don't understand the visitor.
There's quite a few sites I visit regularly take the 'automatic with optional full site approach' including this one.
The only issue I have with this scenario is when (in most cases) the link to the full experience is tiny and hidden away, if the site doesn't remember the choice if I select full site, and in many cases the decisions of what content to prune for the mobile experience prove too limiting forcing a switch to the full site.
I definitely think a server-side solution is the best approach but it's not always possible to apply so you could find helpful using a JS script. I wrote a script that redirects the user to the mobile version of the site, you can find the source here: