Device Atlas API and Django-Admob
I dream of the day when others code to my API and I sip scotch.
Until then I started two new projects working on other people’s APIs this week.
First I’ve taken a swing at re-imagining the Device Atlas Python API. The existing Python API does the job but the exposed method calls are ominous (`getTreeFromFile`? `getProperties`?) and the returned dictionary objects leaves a bit to be desired. There is also a rather large chunk of what I would consider cruft for dealing with typed and untyped properties. The new API looks like this:
Check it out under `deviceatlas` on github.
Second I’ve written a Django pluggable app for AdMob ads and analytics. I coded a simple snippet some time ago - this is more of the full meal deal and sets AdMob cookies and other wonderful things. The backend code is based off the Ruby AdMob Gem. Check it out under `django_admob` on github.
February 14th, 2009 at 1:44 am
I never knew that there was DeviceAtlas API for Django, so far I have been using WURFL in djangobile (http://code.google.com/p/djangobile/), but I would like DeviceAtlas formed part of procces of device detection.
Although the ideal would be to implement the interface proposed by the W3C (http://www.w3.org/TR/2008/PR-DDR-Simple-API-20080917/).
February 24th, 2009 at 3:00 am
@versae DeviceAtlas has had a Python API for some time though 2.3 compatibility is still in the works:
http://deviceatlas.com/downloads/beta
Thanks for the link to the W3C simple API - I find it interesting that these methods appear verbatim in the original Device Atlas API. Most (web) programmers are looking for higher level functionality from their device library - for example - what kind of video is optimal to serve to this phone? While you can get this information by querying a number of properties on WURFL or Device Atlas, an ideal library would present these most common use cases as higher level functions!
Cheers,
John