Archive for the 'mobile' Category

Daylight savings…

My phone, on the Optus network, is set to use network operator time. The screenshot above was taken at 21:43. I’m skeptical about the carrier’s the phones themselves.

( is very cool)

Update: I just noticed that Wordpress thinks daylight savings has ended also:

Wordpress and daylight savings

Youtube WAP site… almost there

I noticed post about a new WAP site that Youtube has just launched. I fired it up on my E61i:

Youtube WAP

Youtube WAP 2

Looks good, except for one thing:

MIME Type correct, URL unsupported

The URL linked to looks like this:

rtsp://rtsp.youtube.com/youtube/videos/fp2FKUOM83U/video.3gp.

My E61i’s browser recognised the MIME type in the URL correctly, loaded up the default 3GP video player (RealPlayer Series 60) which doesn’t appear to do .

This highlights the pitfalls of mobile content. We’ve just about got it right on the desktop browser with Flash being cross platform, but it seems that we’re back to square one when it comes to media content on phones. There’s , RealPlayer, etc. all vying for our attention, and no mobile web browser willing to support any one of them. Doesn’t it feel good to be back in 1996?

I don’t think the iPhone will be the either, but it will definitely help. Besides, there’s no in its version of Safari either. Oh and who hates that ad claiming that the web is the Internet? (that’s another topic for a blog post).

A phone type ’sniffer’?

This about an interesting service called on CrunchGear contains the following quote:

By adding a “sniffer” that determines which phone a person accessing the survey is using, the server can feed pages to the user that are optimized for their phone’s particular browser, in WAP, HTML, WHML, or whatever else will be the fastest and most reliable method. This means that one of the biggest hurdles of mobile Web browsing, compatibility, is no longer in the equation.

Is it really that hard to determine which phone type is accessing an HTTP server? No. The phone type is contained in the user agent header that each WAP browser sends in the HTTP request.

Here’s how to capture the user agent in . request.META is a dictionary of all available HTTP headers. The request object is available in any view. Here’s a simple example:

def get_user_agent(request):
    user_agent = request.META['HTTP_USER_AGENT']
    return HttpResponse("Your user agent is: %s" % user_agent)

If I access this view using my Nokia N73 I get the following:

Your user agent is: NokiaN73-1/2.0 (2.0628.0.0.1) S60/3.0 Profile/MIDP-2.0 Configuration/CLDC-1.1

The interesting thing is what you then do with this to determine device capabilities and subsequently serve the appropriate content.