|Redesigning my website for BlackBerry|
Doomed to duplicate content, or is there a workaround?
| 2:55 pm on Oct 29, 2007 (gmt 0)|
I have been tasked with optimizing our company website for BlackBerry users.
One of the first things I have noticed in researching is that the default setting for the Blackberry is that CSS and JS are turned off.
So much for media="handheld", correct?
Is there some other way to deliver the same content in an optimized way to BB users, or will I have to redirect them to new pages specially made for them?
I am sure this has been asked & answered many times, but I have been searching and so far I haven't found anything specific to the Blackberry here.
Maybe someone can point me to a thread or have mercy on me and repost? :D
| 4:41 pm on Oct 29, 2007 (gmt 0)|
I assume that the User-Agent header can be used to uniquely identify Blackberrys.
(Hmmm... is it "Blackberrys" or "Blackberries"...)
| 5:19 pm on Oct 29, 2007 (gmt 0)|
Interesting, I'll investigate the User-Agent header next. Thanks!
However, I'm still stuck with what to do next.
Even if I have identified that the user is on a BlackBerry, I assume I can only redirect them to custom made content?
I get the feeling that this is the case no matter what, but my boss seems against creating more content, and wants a magic bullet to convert what we have into something Blackberry-browser friendly.
| 6:03 pm on Oct 29, 2007 (gmt 0)|
|my boss seems against creating more content, and wants a magic bullet to convert what we have into something Blackberry-browser friendly. |
Dissuade your boss:
Your site is designed for the big screen. Blackberry isn't the big screen.
Focus on what is important to your mobile users. Their usage patterns may be far different than those of your big-screen users. If they are sufficiently different, you may want to consider a completely separate site.
|if I have identified that the user is on a BlackBerry, I assume I can only redirect them to custom made content? |
There's certainly no need to redirect. Simply serve different content. That is, no need to waste time and resources on a redirect to another page, when the server can respond directly with appropriate content.
Depending on the nature of the particular page, and the target device, this can be as simple as substituting a different style sheet. Let's take the case of simple articles, with no pictures. In your case, though, since apparently the Blackberry doesn't support CSS (or, doesn't by default) it won't be quite so simple. So, you'd want to reformat the article for the Blackberry's screen. Perhaps break it into pages the size of a Blackberry screen. That even is probably more than necessary, as by default text flows to the width of the screen, and vertical scrolling is easy and expected by users. Certainly, any multiple-column or fixed-width layout must go, though!
While you can't use CSS, if you use a CMS on the server end, you may be able to simply write a different server-side template for article presentation on the Blackberry.
In the case of images, you may want to have lower-resolution images that are substituted for the full-resolution ones. Or, this might be done on the fly using something like Image:Magik. Or skip the images.
Maybe your users won't want to read articles on their Blackberry. You may have some particular interactive feature (say, for example, airline flight delays) that is of particular interest to them. They probably aren't interested in reading about how to pack when they are already in the cab stuck in traffic on their way to the airport. So, make sure you that feature is clearly featured on the home page for your Blackberry users, and make sure that the lookup form that you serve them is optimized for the Blackberry screen.
I'm assuming that there's something uniquely appealing about the Blackberry device to your users. Otherwise, your efforts might best be directed toward more general optimization for mobile devices.
| 7:19 pm on Oct 29, 2007 (gmt 0)|
Thank you very much for the information, jtara.
You mention something that should have been obvious to me at the start... What would handheld users primarily want with our site?
It occurs to me that the much more efficient path is to recreate not only optimized layout, but the content itself for a few specific pages of our site, and forget a one size fits all fix for hundreds of pages that will, in all likelihood, never be browsed by a phone in the first place!