Development

There are two technical approaches that can be used to detect mobile devices: On-Premise and Cloud based. This blog explains the advantages and disadvantages of each and provides free source code to enable you to evaluate which solution is right for your organisation.

At 51Degrees.mobi we aim to retrieve accurate information about every device that we use in our database. Our professional team use a combination of sources including: Official websites and technical documents, unofficial mobile news websites and physical devices to create the most comprehensive list of device properties available.

This blog will describe how to implement 51Degrees.mobi properties client side by generating dynamic JavaScript from the server using 51Degrees.mobi device detection capability. For example; The follow code could be used to perform an action if the screen diagonal dimension is more than 5 inches.

if (feature.ScreenInchesDiagonal > 5) {....}

51Degrees.mobi is compatible with the Zend developer cloud, "PHPCloud", without the need for php extensions. This short guide will show you how to implement the 51Degrees.mobi PHP device detection API using the developer cloud.

51Degrees.mobi is compatable with the Zend Framework without the need for plugins. In this short guide, I will show you how to implement the The 51Degrees.mobi PHP device detection API into a Zend framework project running on a Zend application server. Although this article has been written with Zend server in mind, the principals will apply to any other PHP compatible application server.

Our PHP device detection API includes a feature to update the rules and data used to identify requesting browsers, operating systems and hardware via a single PHP script (51Degrees.mobi.update.php). Plug-in developers want to use this script to provide a simple button to update the device data from within their favourite CMS' administration interface. However our update script simply writes status messages back to the browser as plain text. Some browsers don't display these messages as they arrive, instead waiting until the entire message has been received. This is no good if we want to provide the user update status messages as the update is happening. For example; "Calculating Delta" or "Verifying Changes". We therefore need a method to display these messages as they arrive. This blog explains a surprisingly simple solution.

This week sees the launch of 51Degrees.mobi's C detection software into Beta. This implementation will assist webmasters with high volumes of traffic to manage. With this first entry, I'll show you how to implement a simple log parser that can produce tailored statistics about device usage from a web server's log file.

This blog briefs on the steps involved in configuring the 51D Framework - .Net Mobile Toolkit with an existing ASP.Net application. These steps are common to ASP.Net web applications based on .Net 2.0 and .Net 4.0.

Integrating the 51D Framework with an existing ASP.Net web application involves configuring the licence key, defining required custom configurations and referring to appropriate version of Framework assemblies.

Let's look at each step in brief assuming you have already installed the 51D Framework - .Net Mobile Toolkit.

This is a guide explaining how to create a mobile web page that contains the nearest 'real world' retail stores to a user's mobile device, based on the current position. There are just 6 simple steps.

A completed project containing the results of these steps is available to download later on in this article. You will need to add a Framework licence key to the bin folder for the project to operate.

Following the showcase of MVC4 at the Build conference this guide will show you how to setup an MVC4 web application to use different Views based on the capabilities of the device accessing the site. This allows you to give all users a perfect experience on smart phones, feature phones, tablets and desktop web sites.