Previously on mobiForge Ronan posted about a lightweight approach to device detection using regular expressions in PHP. Since this is still an approach widely adopted by many web developers today, we feel that it's about time we revisited the original article.
Device Detection - Posted by ruadhan - 19 Jun 2010
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!
The dotMobi WordPress Mobile Pack is a complete toolkit from dotMobi to help mobilize your WordPress site and blog.
It includes a mobile switcher to select themes based on the type of user that is visiting the site, a selection of mobile themes, extra widgets, device adaptation and a mobile administration panel to allow users to edit the site or write new posts when out and about.
We've just gone live with an new version of the ready.mobi API. (Full details and code samples here). So what's new in this version? The most notable feature in this version is the ability to post markup directly to the ready.mobi API without having to supply a publicly accessible URL to the service.
This is the result of some early feedback on the API that during the development cycle pages often did not have a public URL, and so they could not be tested with ready.mobi.
In the words of the developers "CodeIgniter is an Application Development Framework - a toolkit - for people who build web sites using PHP. Its goal is to enable you to develop projects much faster than you could if you were writing code from scratch, by providing a rich set of libraries for commonly needed tasks, as well as a simple interface and logical structure to access these libraries. CodeIgniter lets you creatively focus on your project by minimizing the amount of code needed for a given task."While CodeIgniter can be considered a small framework compared to competitors such as Zend Framework, it comes with all the basic libraries that we are all using in every single project we develop.
Content Adaptation - Posted by James Pearce - 08 Dec 2008
This article follows on from last month's Part I, where we discussed some of the principles of handling mobile users and switching their experiences. If you haven't read it yet please do so before we dive into some of the technical ideas and implementation details.
In the past, delivering content to mobile devices has been a very tricky subject. Developers who came into the mobile world were usually confronted with a new and unknown paradigm, where very little information could be found on how to determine devices' capabilities and to deliver content to them.
Content Adaptation - Posted by svo9712 - 31 Mar 2008
In this article we look at image adaptation using the DeviceAtlas API. For the mobile web it is often important to provide device specific images with correct format and size. Here we describe an Image Adaptation API, developed by Muntasir Mamun Joarder which makes use of the DeviceAtlas PHP API to to convert images on-the-fly into a format and size appropriate for the requesting device.
Device Detection - Posted by adrian.hopebailie - 28 Mar 2008
We have just released version 2.3 of our API as a Beta with a whole host of new features that make integrating it into any PHP website much much easier. The new API also does all the hard work described in this tutorial for you, so stop reading and check it out. The download comes with extensive samples and documentation to help you get started too.
Find out more...
(Part II in a two part series. See Part I )"DeviceAtlas is the world's most comprehensive database of mobile device information." [deviceatlas.com]. The database comes with an API that developers can use to determine the capabilities of devices browsing their website and in so doing adapt their content to make it suitable for the user’s context. Part II of this tutorial will point out some of the challenges that developers may encounter in implementing DeviceAtlas such as user agent "sniffing" and data caching for increased performance. It will also provide possible methods to address these challenges and a few examples of these.