• About Us
  • Blog
  • Basket
  • Account
  • Sign In
  •  

Blog

21

Jul

2015

Memory and Performance Impact of 51Degrees

Load testing 51Degrees with DotNetNuke CMS

The purpose of testing is to investigate the impact of 51Degrees device detection and image optimisation modules on the performance of the DotNetNuke (DNN) Content Management System. The DNN platform was tested with high user page loads. DNN was chosen as a representative .NET platform for testing 51Degrees .NET API.

This article providea a table of expected memory consumption for common configurations.

Comments (0)

17

Jul

2015

Image Optimizing for Loterie Nationale

How Image Optimizer Works

Loterie Nationale use 51Degrees image optimization for onsite advertisements (e.g. banners with next draw jackpot) in order to provide the right image for the right screen and lessen some of the burden for people that manage image assets internally.

Comments (0)
Read more

Categories: Development, Device Data, News

Tags:

15

Jul

2015

API Version 3.2 Update for Developers

Details of features and release schedule for API updates

We’re always working hard to improve the 51Degrees APIs making them easier to use, consume fewer resources and provide new features. Version 3.2 combines many incremental changes. Highlights included in all API variants are:

  • New version 3.2 data file is 25% smaller than version 3.1. Data file size is no longer proportional to supported Device Combinations and Signatures. As a result V3.2 data files will grow at a slower rate than V3.1.
  • C APIs now join PHP, .NET and Java in supporting multiple HTTP headers, not just User-Agent. The developer no longer needs to consider which headers to use.
  • Cache structures are now all memory limited rather than time limited resulting in a more consistent memory profile.
  • Information relating to false positives such as rank information is returned more quickly.
  • Github is the master repository for all API source code. Mirrors will be maintained on Codeplex, Sourceforge and other locations.
Comments (0)
Read more

Categories: Development

Tags: API

8

Jul

2015

Device Detection for Apple iPhone and iPad

Which techniques to use and avoid

Author: Anonym

51Degrees data analysis team stress tested a range of real iPhone and iPad devices, both old and new using all the major web browsers in order to determine if CPU stress testing is a viable additional method to identify iPhone and iPad models alongside User-Agent analysis, screen information and WebGL API

The full results are available for download along with the analysis of the differences between each device and browser.

Comments (0)

18

Jun

2015

List of all Web Enabled Devices and Associated Browsers

Use the 51Degrees .NET API to return meta data about device combinations

Many 51Degrees customers are using the consistent and high quality meta data within 51Degrees to drive related reporting solutions and user interfaces. This blog post contains a short C# code snippet for returning related unique combinations of meta data values. It's intended to show how easy such queries are to produce in .NET with 51Degrees and provide example code for those wishing to access device meta data.

Comments (0)
Read more

Categories: Development

Tags: C#, .NET

4

Mar

2015

51 Degrees Java API now also available on Scala

Using 51Degrees device data with Scala and Maven

Author: Anonym

Scala is becoming increasingly popular as it allows concise code with a strong type system. It can also access all Java libraries as it runs in the the Java Virtual Machine (JVM). In this blog we'll use the 51Degrees Maven Java library to perform device detection using Scala code. The blog assumes the reader is familiar with Maven and Scala.

Comments (0)

25

Nov

2014

Calculating Detection Speed

How do we know each detection only takes 0.0016ms?

Learn how we obtained the figure of 0.0016ms average time for a single detection. Verify this figure on your system in 4 easy steps.

Comments (0)

12

Nov

2014

Upgrade Google Analytics

Enable Multi-Screen Tracking

Analytics techniques haven’t kept pace with the rapidly evolving techniques of Responsive Web Design (RWD) and server side adaptive design. Google Analytics will provide information about the device model (i.e. iPhone or Galaxy S4) or whether the device is classified as a mobile, tablet or desktop, but this isn’t often sufficient to make informed design decisions to improve a web page or site. Consider click through rate (CTR) on advertising. How do you know if adverts on a 3 to 4 inch diagonal screen performs better or worse than a 5 to 6 inch diagonal screen? You don’t without some enhancements.

Comments (0)

24

Oct

2014

Redirection in .NET

Not only for mobiles

In this article you will discover that 51Degrees for .NET can be used to redirect any devices, not just the mobile ones.

Comments (0)

17

Oct

2014

Get more from responsive web design with device detection

Overcoming the "all device types should get the same content" problem with RWD

Author: Mike

Responsive Web Design solves many of the layout problems associated with increasingly diverse screen sizes but is constrained by one hard to justify assumption. RWD assumes all devices should receive the same content and support the same business processes. Read on to understand methods to optimise your RWD web site for mobiles, tablets, smartphones, and TVs.

Comments (0)
Read more

Categories: Development, Opinion

Tags: RWD, RESS, HTML5, CSS3

RSS
12345678