• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Mobile version of website advice

Status
Not open for further replies.

morkus64

Diamond Member
So, I'm wondering the best way to go about making a mobile version of my site. I'm aware that you can do things like detect the browser resolution of the visitor and use different css, but i think i'd prefer to keep the two fairly distinct, as I might change up the content on one versus the other.

Can I detect the resolution and then if it's less than say 480px (or better yet, detect the device?) and then send them to m.mysite.com?

As for building the site itself, what do I need to keep in mind? Is there a good builder specifically for mobile sites out there that actually lets you keep the source code (I want to host it, not use a winksite or whatever)?

Any other tips are greatly appreciated.
 
You can probably detect what browser they are using and redirect base on that. I wouldn't do it base on resolution because any device can be lowered to a mobile resolution. I am pretty sure Safari Mobile, IE Mobile, etc. gives off different user agent vs their desktop counterpart.
 
Look at the request headers of the incoming request and inspect the User-agent field. You will be able to figure out if they are using a mobile browser from that.

http://detectmobilebrowser.com/ has scripts for nearly every language and environment you'd be using. It wouldn't hurt to check for window resolution, but you might catch desktops, laptops, tablets etc in the filter which might undesirable for some people.
 
We actually just launch at a mobile site for my company. Our basic rules are to redirect to m. if it is a phone while tablets still go to the main site. We actually had Akamai do this for us since they are our site accelerator and all requests go to them first. The biggest trick is keeping up with all of the new OS and devices being launched. I know we can tell the difference between an iPad and iPhone or an Android phone or a Honeycomb tablet.

As far as mobile site, keep it basic, low resolution images and prevent unnecessary wrapping of text at iPhone resolutions and everything else will be fine.
 
The whole idea of a "mobile version" of a site is in flux. Many mobile devices will expect to get the full version of your site. This includes nearly all the current crop of smart phones, and all the current tablets. Your big decision, imo, is whether the current user is capable of displaying the full website. If not then you return them an altered rendering.
 
Some plugins do okay with rendering a website compatible via mobile media. And these plugins do make it a point of making your website compatible to different mobile devices as well as update their plugins. When all else fails professional web designers are always an option.
 
The whole idea of a "mobile version" of a site is in flux. Many mobile devices will expect to get the full version of your site. This includes nearly all the current crop of smart phones, and all the current tablets. Your big decision, imo, is whether the current user is capable of displaying the full website. If not then you return them an altered rendering.

I agree. There are so many reasons why a "mobile version" is a bad idea. It seems like a leftover idea from the last decade or two. Responsive design is definitely a better idea IMO.
 
Status
Not open for further replies.
Back
Top