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


Apple Standalone on Device Detection

Published on Wednesday, July 8, 2015

Apple Standalone on Device Detection

Exposing the crippling solution used to detect iPhone and iPad models

For the latest instructions on how to detect Apple iPhones and iPads please refer to this blog

Device Detection is among the best techniques available to optimise websites for multi-screen. The power of the web server and the web browser are both utilised to deliver the most appropriate processes and screen layout for each device category. When combined with Responsive Web Design (RWD) the resulting improvement in user experience leads to visitors staying for longer and spending more.

Example Euro Millions lottery game card for different devices - see Loterie Nationale Case Study

Apple are Different

Device vendors as varied as the mighty Samsung, to brands like Pantech and Micromax all recognize the importance of supporting this distinction between devices. Information about the model of the device is embedded into the data sent to websites. However, Apple do not fully support this approach.

As a result, a more complex process of identifying Apple devices is required by device detection solutions like 51Degrees. Measuring the ratio of screen height and width, plus examining the pixel density provides insight into the iPhone model. It reveals most of the important information needed by website owners to differentiate by screen size.

However, the technique is not without its problems. Detailed examination of Apple iPhones and various web browsers by the 51Degrees data analysis team shows that an iPhone 6 plus in zoom mode shares the same reported screen information as an iPhone 5. Where screen sizes are similar such as across the 5 and 5c it’s not possible to tell the devices apart.

The technique does not work for iPad’s where the reported screen information is almost identical across most models.

Desperate Device Detection

Some device detection solutions have tried to address the problem by artificially stressing the iPhone or iPad to determine how quickly its processor can complete iterative tasks (Micro Benchmarking). Understanding how the device performs under stress provides an indication as to the CPU used and therefore the model of device. The approach can yield more information but ironically at the expense of user experience as the page load time increases and the battery is drained more rapidly.

Example analysis of stress tests performed on newer iPads

Competitors who adopt this approach acknowledge up to 100ms processing times. In reality on older models, the delay could be much greater. The concept is terrible in theory and awful in practice. 51Degrees have never used this approach. We choose not to. A full technical analysis covering all Apple iPhone and iPad products and all the major browsers (at the time of publication) is available here.

Request to Apple

If every web site were to stress iPhones and iPads to gain model information the web would slow down for Apple users. This isn’t in Apple’s interest. Fortunately, only a minority of device detection solutions currently utilize stress testing.

The need to use such techniques would be eliminated if Apple were to make a very simple modification in a future update of iOS and provide the information they already provide to application developers to web developers. Such a move would bring Apple into line with all other major device vendors.

In the past when most iPhone’s and iPad’s shared the same screen information the problem was annoying but not critical. The arrival of the iPhone 6 has made the issues more pressing. Perhaps Apple have not considered the need to change their policy. Now would be the time for Apple to do so before those less responsible than 51Degrees slow down the web for Apple customers.

Read Full Analysis

All code and methods shared in our blogs are only relevant as long as Apple do not block the information that can be accessed.

Try 51Degrees today to add detailed device information to your website


Get Started

Comments (0)
James Rosewell

James Rosewell

Other posts by James Rosewell
Contact author



.NET 4G 51Degrees 5G Acer Adform Adtech Advertising Afilias Alcatel Amazon AMP Analysis Analytics Android Apache API Apple Asian Market ASP.NET Asus Blackberry Browser C C# Centro Chrome chromium Client hints Cloud CMS CPU CSS3 Data Data Blog Data File Daydream Design Detection Developers Device Device Data Device Detection Device Intelligence Device Models Device property DeviceAtlas Disney dmexco DotNetNuke Download ebay Ericsson Event Facebook Firefox Foundation Framework Galaxy git repositories Google Google Analytics Google Daydream GPU GSMA Guess HAProxy Hash Trie HTC HTML5 HTTP HTTP Headers Huawei Infinix Ingeniux Internet usage iOS iOS 13 ipad iPadOS iPhone iPhone 11 Java Javascript Kentico LG Liferay LTE m.dot Memory Memory leak Meta Data Microsoft Mobile Mobile Analysis Mobile Analytics Mobile Devices Mobile Marketing Mixer Motorola Mozilla MWC MWC 2017 MWC16 Native Apps NET New Release News Nexus NFC NGINX Nokia OnePlus 5 Opera Operating System Oppo Optimisation OS Patent Performance PHP Press Release Price Band programmatic Publishers Python Redirection Research Responsive Images Responsive web design RESS Review RTB RWD Safari Samsung Scala ScientiaMobile SEO Server Server-side optimisation Seznam.cz Sitecore Smart TV Smartphone Smartwatches Sony Swedish Beers Tablet Tencent Testing Tips Tutorial Umbraco Update User Agent User-Agent Valgrind Varnish Varnish Cache Video Vodafone VoLTE Web Web Apps Web content management Webtrekk White Paper Widgets WiFi Windows WURFL Xiaomi Xperia ZTE