Mobile Film Festival

Mobile Film Festival
Mobile Film Festival
du 3 au 15 janvier 2006

Du 27 octobre au 20 décembre: réalisation des films et téléchargement sur le site. Tous les films peuvent être visionnés en ligne.

Du 3 au 15 janvier 2006 : le jury du festival composé de professionnels du cinéma et de l’image visionnera la sélection officielle et décernera trois prix – meilleur film, meilleur scénario et meilleure idée originale.

Accessing mobile sites

(Extracts of a discussion on the w3c mobile mailing list)

Accessing mobile sites is not easy. To start with user has to remember two url’s, one for normal and one for mobile access. TV, radio, ads, they all promote URLs and it would be very difficult to promote two URLs.

The best way would be to provide just one entry point, ie. the same URL for EVERY device with the web server choosing the right content depending on the device.

Even then it is still difficult to enter an URL on small 12-keys keypad. What can be used alternatively ?

  • Shotcode, Semacode, QR code or any 2D barcode
    This require a software installed on the mobile AND some proximity with the announcer (does not work for radio for instance)
  • (Suggestion by Scott Weiss from “Handheld Usability”) Setting up a new standard for mobile site URL: start with a star (‘*’) and the rest of the entry indicates a URL. That URL would be all digits, and could be a pseudonym for a text-based URL.
    For instance: *52992, also known as *KAYWA could take one to the mobile version
    http://www.kaywa.mobi
    If the .mobi domain does not exist there could be a universal lookup.
    The idea is not that bad. Require a new standard. It already exists on Gallery where every mobile site can be accessed through a “Short code”
  • (Suggestion by Shahriar Karim from Nokia) Using T9 recognition with a customized dictionary seeded with http:, .com, .net, etc. as well as common sites such as CNN, Yahoo, Google and completed by the user.
    Already on the market on Sony/Ericsson phones I believe
  • Voice recognition (will come).

What else ?

I guess we will see all solutions. I wonder what usability pundit think about this problem.

Mobile Web Best Practice: Establish the Context of the Device

A few weeks ago I wrote about the w3c releasing a working draft on the Mobile Web Best practices. I read it and at the end I found myself quite happy with what we have done with our mobile blogs. Of course there is still room for improvement but we have already implemented almost all the best practices, sometimes even more. I thought it might be interesting to go through a few of them in a “Mobile web Best Practice” serie.

Implementations should take all reasonable steps to find out about the device/browser (client) capabilities, adaptation and other transformation that takes place for any instance of an access to a ressource.

Techniques > CC/PP, UAPROF, CSS Media Queries, DDWG output, DIWG material, Wurfl,…

@Kaywa > We use the latest. I found out about Wurfl when developping iFeedYou and bring it at Kaywa. WURFL is “just” a XML file that contains all informations in a hierarchical way needed to establish the context of the device. It contains actually much more information than we need so we use a lighter version that contains only the informations to determine what markup should we serve. It is also used to determine the screen size to resize images and for a few other things.

Since on KAYWA blogs you can also publish sound and video (also by MMS or email) we will also in the futur let know the user if he can read the media on its mobile or even better transform it.

Written by Comments Off on Mobile Web Best Practice: Establish the Context of the Device Posted in Misc