Developing, Content Adaptation

Device Diversity

ronan — Thu, 07 Jul 2011 11:08:36 +0000

As dotMobi brings DeviceAtlas to the cloud Ronan Cremin, Director of Engineering at dotMobi, charts the increasing complexity of the device landscape for developers in the first of two pieces looking at device fragmentation.

In the beginning the web was a much simpler place. By the time the web was becoming a mainstream media in the late 1990’s there was only one device through which you accessed it: the humble desktop PC, running one of just a handful of browsers.

Future of the Mobile Web

mclancy — Fri, 03 Feb 2012 12:13:12 +0000

Last week we hosted an event loftily entitled "The Future of the Mobile Web" at the Dublin Convention Centre.

The best of breakingdevelopment conference

ronan — Thu, 15 Sep 2011 09:45:40 +0000

As many of you know, the breakingdevelopment conference took place in Nashville, Tennessee over the last few days. It appears to have been a really seminal conference with 13 leading mobile web developers speaking.

Others have already put together summaries of the conference but I thought I'd link to what I thought were the most interest presentations.

DeviceAtlas & jQueryMobile

daniel.hunt — Sat, 16 Oct 2010 06:00:00 +0000

The first Alpha release of jQueryMobile was announced today, to great fanfare, and the mobile web world is already on fire with the thoughts of what this will mean to them.

A little bit of background...

Originally developed by John Resig, jQueryMobile's big brother "jQuery" is now in use by pretty much anyone who implements advanced JavaScript capabilities on their site.

Mobile Web Development & Device Detection

daniel.hunt — Thu, 23 Sep 2010 10:02:06 +0000

Peter-Paul Koch, also known as @ppk, has posted a three part blog-post on the State of mobile web development [ one | two | three ], in response to Mike Rowehl's recent (correct & justified)

Device Detection in the Cloud: DeviceAtlas Personal

ruadhan — Sat, 19 Jun 2010 14:49:20 +0000

In this article we offer full tutorial on how to use the preview release of the service. So what is DA Personal?

The purpose of DeviceAtlas Personal is to make device detection even easier. The main difference between DA Personal and DeviceAtlas, is that Personal is a Web service. It works as follows: a user visits your Web site on his mobile device. You then forward the User-Agent HTTP request header to the DA Personal service, and the response you receive will contain information about the user's device. That's it!

A minimal mobile-aware web app with Python & cloud-based device detection

ronan — Mon, 21 Sep 2009 14:44:05 +0000

In this article we'll look at a how to make a minimal device-aware web application. The point of this article is not to demonstrate a useful application but rather to show just how little code is required to make an app that is fully device aware, and that can change its presentation entirely depending on the nature of the device accessing it.

The Beauty of Mobile Device Data

ronan — Wed, 16 Sep 2009 15:13:52 +0000

Recently at dotMobi we have been investigating how to make our DeviceAtlas device detection even better, while at the same time trying to keep the size of the distributable database as compact as possible. As some of you may know, DeviceAtlas uses a tree of data stored in a very compact JSON file to distribute our device data knowledge. The actual format of this JSON file is a Patricia tree organised around the user-agent strings of the devices that we have data about.

User-Agent Switcher for Safari 4

atrasatti — Tue, 30 Jun 2009 15:57:26 +0000

The User Agent Switcher plug-in for Firefox has been a GREAT add-on and we all love it. 1 year and 27 weeks ago Ronan wrote a really simple, but useful configuration file for it that is available here on mobiForge (if you use Firefox it's a MUST: User Agent Switcher config file).

Mobile Web App Development with ASP.NET and HAWHAW

H2f — Tue, 23 Jun 2009 15:24:01 +0000

Development of mobile applications is often highly dependent on the target platform. If plain old XHTML markup is written from scratch then it is rather easy to switch between platform and technologies. But if the development process has been accelerated and made comfortable by the use of tools and middleware, it soon becomes difficult or impossible to switch environments e.g. from a LAMP environment to ASP.NET or vice versa.