Tuesday, July 27, 2010

There's an App for That, but Should There Be?

[My rationale for the CFM International Mobile Website strategy]

By now, everyone seems to recognize that their website should perform well for the increasing number of mobile viewers out there. There's an app for that, right?

Well, we are about to be inundated with a pile of similar yet incompatible mobile platforms and App Stores.  Just to name a few, we have:

  • Apple iPhone
  • Google Android
  • Blackberry
  • Nokia Symbian
  • Microsoft Windows Phone 7
  • HP WebOS
  • Samsung Bada

AND that's just the capable phone platforms.  AND that is excluding carrier operated App Stores like Verizon's V-Cast App Store.  AND that is excluding the tablet operating systems, which browse more like a desktop than a phone anyway.

So you want your website to perform well on mobile, but do you really want to develop 7 distinct native apps and maintain those apps?  Plus, do you really expect your customers to take the time to install an keep an app updated, just to look at... A website???

The smartest and savviest website operators are investing their time and money into making their site deliver mobile friendly content.  Look at ESPN or Engadget on your mobile and see what they did. 

We were faced with a similar challenge when CFM wanted to make a mobile friendly site ahead of the Farnborough Air Show this month.  The mobile strategy we developed is a simple and effective one, and can be applied to many sites out there:  

  1. Choose an effective browser detection library which works with your website's framework.
  2. Enhance the existing CMS to support a Default Desktop Template as well as a Mobile Phone Template.  It's important that the Desktop template be the true default so as not to interfere with SEO.
  3. Enhance the "Desktop" template to include some tablet/iPad specific hooks (to provide alternate to flash content).
 
The advantages of this method are obvious (but why not spell them out!).  Up front development is greatly reduced because you don't have to code proprietary apps.  Maintenance is reduced because a single CMS controls all content  for all users.  And the end user is easily able to view your content, by standard conventions that are compatible across all platforms.

So there you have it... Complexity, simplified!

More Info: CFM Mobile Website
More Info: Case Study on Cicada's Website

Monday, July 19, 2010

Welcome to 1990, Linux!

We have HUGE news for the Linux UI today!

At LONG last, the God awful font rendering (and especially kerning) issues should be going away.  For instance all the web fonts, including Microsoft ones should look better, and more in line with the way they appear on Windows and Mac OS.

http://apple.slashdot.org/story/10/07/19/1524250/FreeType-Project-Cheers-TrueType-Patent-Expiration?art_pos=6

Here are some side by side comparisons found in the original article:
I'm definitely interested to find out how these work out.  This was one of many big reasons I moved back to the Mac.  I swear it felt like my eyes were crossing when I was using Linux so a lot of times I'd just do things in Monospace font!  It's unreal that I put up with it for so long.

I'd love to hear from anyone who has seen the update pushed by either Ubuntu or Fedora whenever they update these packages.  Hopefully they don't wait to make the necessary configuration changes instead of waiting until the next release.