I’ve written a few posts lately about what not to do when you do not have great support for your mobile- or tablet visitors, one about not prompting app downloads and one about what you should not to when you don’t have a tablet strategy. But what I haven’t covered is what you should do to support mobile and tablet visitors, because there are so many answers to that question and it all depends on your goals. But here is a start a suggestion on what you should do while developing a better solution or deciding on your strategy.
Develop a page for mobile and/or tablet visitors with the options they have.
A few examples could be.

- Link to your full website
- Link to an app download
- Link to a mobile version of the site
- A reminder to send themselves about visiting the site from another device later.
An example from Google:
I was inspired to the last example when visiting the chrome extensions site from an iPad. When I visited the webpage I was greeted with a message saying that I could not access the website from my operating system but I could easily send my self a reminder to try again later from a desktop. I loved this solution as it gave me an option, thus the key takeaway is – don’t leave your visitors stranded even when you don’t intend to help begin supporting a channel.
For example; IKEA recently launched a new mobile website based on html 5 which I tried to visit from a windows phone 7. Only to be met by a white screen. Why? Windows phone 7 does not support html 5. If Ikea did not want to support window phone what they could have done was redirect the visitors to their normal website or give them a page with alternatives such as the one’s above.
Do you have another view on this? Prefer another user experience or have other ideas for alternatives? Please drop a comment.











Recent Comments