Monthly Archives: February 2010

Mobile-izing an Existing Site

There has been a lot of talk amongst my clients lately on how to make our existing sites more mobile device compatible. We have done some brainstorming, and have come up with some ideas on how to do this.

Build a separate site

The simplest thing to do would be to do build a separate site for mobile users. Some simple user agent switching based on the user’s browser can take mobile phone users to the separate site. The new site can then be tailored for smaller screens, be less graphics intensive, and develop alternative solutions for Flash components.

Full Redesign of the existing site

Another possibility would be to build one site that has enough logic to manage multiple resolutions. This could be through multiple master pages, separate sets of images, JavaScript to display different image sizes, different CSS files, and a fluid CSS based layout without tables. This can be cumbersome and time-consuming, but may be a good approach long term. This will accommodate both large monitors on desktops, smaller resolutions on netbooks, and tiny resolutions on mobile phones.

Hybrid approach

One approach we are considering is a hybrid approach, combining the strengths of the first two approaches. If we have two domains with user agent switching, we can optimize each of the sites – one for mobile users and one for full browser users. Each site could have its own master page or template with its own separate set of images. We can reduce the work by tagging the reusable content with specific div or span labels, and reuse them on the mobile site.

Build a Mobile App instead

Building a separate mobile application for each of the major phone platforms would allow the development team to tailor the user experience to the individual phone. Delivery to the phones and advertising the mobile application may make the user base smaller. We would also need to develop across at least 4 different platforms – Android, iPhone, Windows Mobile, and Palm. There are multiple versions of the platform to manage, as well. The phones that use a custom platform would then miss out on the entire mobile experience.

Invest in a tool or 3rd party

There are lots of third party tools that can be used to help migrate or transform your site into a more mobile friendly experience. Some of the companies who develop and support these tools either have fully managed solutions or have a consulting services group that can be hired to help you through this process. There are also a lot of companies who say that they specialize in mobile-izing sites that you can contract with, and I am sure they are not cheap.

Do Nothing

The further technology advances, the more this option becomes really viable. The iPhone’s browser has multi-touch pinch-to-size technology, allowing you to zoom in and out of the HTML page. The Android is releasing this as well very soon, but in the interim has a zoom feature. Even the old Windows Mobile 6.0 phone I used to use had a custom browser with zoom technology for the pages it rendered. the more improvements in technology, the less developers will need to customize based on resolution.

What are your thoughts?

What are you or your team doing to break into the mobile arena? Do you prefer one of these solutions over another? Do you have another idea or approach you would use? What tools or 3rd parties are you using to mobile-ize your site? Leave your thoughts, ideas, or experiences here and share with others!
Advertisements