Building IWC.com: Our Approach to Video

IWC.com features a great deal of content which includes some amazing videos. Two great examples of these videos can be found on the Aquatimer family page. Galapagos is an eight and a half minute video highlighting IWC’s longstanding relationship with the Charles Darwin Foundation and includes some really incredible cinematography. Don’t miss the footage of iguanas foraging underwater. A little further down on the Aquatimer page is a short animation demonstrating the engineering behind the depth gauge within the Aquatimer Deep Two. It is an example of how IWC uses video to educate customers about their watches.

Galapagos video on the Aquatimer page

As the second installment of our series on building IWC.com, we’re looking more closely at how this video is delivered to both desktop and mobile browsers.

via Odopod – Building IWC.com: Our Approach to Video.

Building IWC.com

IWC.com and the publishing system powering it are a new cornerstone for IWC’s digital strategy. Given the goal that this system remain relevant for a minimum of 10 years (and what can happen on the internet in 10 years) technology choices were particularly important.

How do you future-proof a development like this?

For us, the logical place to start is with technologies that are familiar, flexible and open.

The standards-based front end delivers a variety of beautiful content to the widest range of site visitors. The content itself is managed by IWC’s internal team, using a sophisticated and easy to use CMS built with the tremendously flexible Django framework.

via Odopod – Building IWC.com.

Mobile web test suite

Peter-Paul Koch published an excellent article on the smartphone browser landscape back in December of last year. It has a ton of great information including advice on building a mobile QA suite. As Peter-Paul points out in his ALA article and an excellent series of articles on his blog, dominant browsers vary region to region. Here is a test suite I recently distilled given my U.S. centric needs:

Primary Phones:

  • iPhone OS4: running Safari and Opera Mini
  • Doid 2 (OS 2.2): running Webkit, Opera Mobile, and Opera Mini
  • BlackBerry Torch (OS6): running Webkit
  • BlackBerry Curve (pre OS6): running BB Browser

Others, included dependent on region and site statistics:

  • Nokia n95 (S60): running Webkit
  • Samsung (Bada): running Dolfin
  • Palm Pre (webOS): running Webkit
  • Windows Phone 7: running IE7

This suite does include browsers that don’t do well with JavaScript (Opera Mini and BB Browser) and phones that use a variety of input devices (touch and non-touch devices as well as hard & soft keyboards). I have not included any of the lowest end browsers (NetFront) because we have not yet worked on a site where significant traffic comes from those devices. For the moment, I’m relying on the powers of progressive enhancement to serve the limited traffic we get from those lowest end devices.