No user agent detection for the iPad Mini

http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent

by dirkdk • 14 years ago

70 64 14 years ago

stephen_g• 14 years ago

Often I feel like it would be better if sites couldn't even tell the difference at all between my phone and tablet and a normal browser... Some mobile sites are great, but only a very small minority. Most times I get redirected to a mobile site, I switch to the desktop version and find it's a far better browsing experience and they shouldn't have bothered in the first place...

An example of this is almost any blog with the WPTouch plugin... Most regular Wordpress theme gives you a better reading experience going to the desktop site and double tapping the main column to make it fill the screen!

tomrod2• 14 years ago

> Some mobile sites are great, but only a very small minority.

Indeed! Wikipedia is a thorn in my side when browsing with an iPod.

dmethvin• 14 years ago

Although the title talks about detecting the iPad Mini, the article makes it clear that the real dilemma is that there is no way to know the physical size of pixels as presented on the screen and size things accordingly. That's especially important on touch devices where you want to size controls to make them finger friendly.

erichocean• 14 years ago

Why not just follow Apple's iOS control sizing guidelines, which are measured in pixels, and are exactly correct for the iPad mini (and slightly oversize for the regular iPad)?

eridius3• 14 years ago

I think that's a red herring. Sure, the iPad mini has a higher DPI than an iPad 2. iPad 2 is 132ppi and iPad mini is 163ppi. But guess what else is 163ppi? That's right, every non-retina iPhone. So if your touch areas are large enough for an iPhone user to use, then it's large enough for an iPad mini user to use as well.

notatoad2• 14 years ago

The size isn't that different: if your controls are small enough that they work on the 9.7" ipad but not on the 7.9" ipad, they are probably too small.

granto• 14 years ago

Would it be helpful to be able to display certain buttons or other elements at a set physical dimension as opposed to pixel dimensions? For example, always show a button big enough for a finger (e.g., 1.5 cm). I ask because we recently launched a web app (www.lifesizer.com) that allows sites to display images in actual life size and think it could be great for designing mobile web sites, but comes with other implications for design, such as modifying layouts for devices with different screen sizes even if they have the same pixel dimensions.

We are currently focused on ecommerce and product review sites, but would love to hear if people think it would be helpful for a new take on responsive design.

Steko• 14 years ago

There are some alternate browsers for iOS that allow you to send a desktop user agent. Sleipnir, Atomic, probably others.

monochromatic• 14 years ago

I just love it when I click on some deep link into a site, and it redirects me to the HOME PAGE of the mobile site, with no way to get to the page I was actually interested in.

jordanthoms• 14 years ago

Yeah, or the sites that say "this content is not available on our mobile site" - so show me the desktop version rather than the homepage!

dmd• 14 years ago

http://xkcd.com/869/

re_todd• 14 years ago

A List Apart had a good article today on this subject: http://www.alistapart.com/articles/your-content-now-mobile/

thedrbrian• 14 years ago

Or any site running the dreadful onswipe.

tamal• 14 years ago

I'd much rather use features that are consistent and that I am familiar with on my device (zooming in Mobile Safari) than every Tom, Dick, and Harry deciding how they are going to cripple their site because User Agent =~ /Mobile/.

dthunt2• 14 years ago

Then just find a way to kill javascript, and the world will finally be sane again.

dancesdrunk• 14 years ago

Precisely - I still fail to understand this need to constantly add the overheads for supporting multiple mobile platforms / devices.

Pinch to zoom / double tap are amazing features made precisely for this - if the text, image or control is too small I just pinch or double tap; takes a fraction of a second and I still get the whole website experience as it was meant to be.

nucleardog• 14 years ago

Until the developer decides he always wants everything pixel-perfect, writes a separate stylesheet for each device/class of device, and locks your zoom.

Fuck you, developer. Let me zoom. It's my device.

Yaggo• 14 years ago

Even big sites such as wired.com and Youtube get it wrong, both refusing to serve certain videos for your flash-disabled desktop Safari unless you fake iOS UA.

tomrod2• 14 years ago

I think this is a case for continuing the current course. By that, I mean that these obvious missing issues of Apple would be fixed in the next revision if a large plurality of websites did not display well. I doubt the websites themselves would be affected in the long term, however. Of course, I base this behavior analysis on a sample of one (my apologies to the staticians out there).

benguild• 14 years ago

They'll probably be able to patch this. Most likely it's a simple oversight

danielsju62• 14 years ago

No oversight, you've never been able to differentiate between device models in the iOS User-Agent. Nothing to see here.

chris_wot6• 14 years ago

The article isn't talking about UA detection, but rather feature detection. In particular, working out the devices ppi.

stcredzero• 14 years ago

> Don’t disable zoom ability in the viewport metatag, such as in user-scalable=no.

Please don't ever do this. It really sucks for reading your site on a touch tablet.

notatoad2• 14 years ago

but please please please, if you're making a site that is even the least bit elastic, do put in a "<meta name="viewport" content="width=device-width,initial-scale=1.0,minimum-scale=1.0">. if you don't put in a min-scale=1, the iPad renders pages at 1024px wide and then scales them down to 768px, making everything unnecessarily small.

jarek• 14 years ago

That sounds like a bug in the iPad browser?

enoughalready• 14 years ago

You almost have to. position:fixed on a lot of android devices won't work without it.

kylec• 14 years ago

The solution to this is to design for the iPad mini. If you make the user interface elements large enough to tap on a mini, they will also be large enough to tap on a full sized iPad. This also has the benefit of presenting a single user experience no matter what size iPad the user has, which I think is a plus.

Firehed• 14 years ago

This.

Follow Apple's human interface guidelines and you'll get this for free. Don't treat them as sacred tomes, but it's no accident that the DPI on the iPad Mini is the same as that of the non-retina iPhone/iPod Touch, and they suggest the same minimum tap target size on both platforms.

The only exception to this is if you're making a ruler, and you're not.

sopooneo• 14 years ago

I agree with you. But I think the argument against this is that the elements will be slightly larger than they need to be on the full size iPad and you are thus not making the most of the available space.

danielsju62• 14 years ago

There is no user-agent detection between any models on iOS in Safari; it's not an oversight. You've never been able to detect a difference between iPad 1. 2, 3, 4 or 2(mini) or iPhone 3, 3GS, 4 and 5, nor should you. User agent detection is horrible and this isn't news.

Downloads over iTunesD show difference though; since you may want to serve them different payloads. "iTunes-iPad/5.1.1 (4; 16GB; dt:77)" vs. "iTunes-iPad-M/6.0.1 (2; 64GB; dt:75)"

chris_wot6• 14 years ago

You are missing the point. It's not about UA detection, it's about feature detection.

malandrew• 14 years ago

Give it a math problem to solve and find our how long it takes to solve it. It's a hack, but that is probably the best way to determine what iOS device it is.

wmf• 14 years ago

It also has the same processor as the iPad 2. And probably the same RAM, so don't go there either.

nerd_in_rage2• 14 years ago

Good. User-Agent detection has always been a hack.

fwr• 14 years ago

How is this good? How is this considered to be a hack? You make this sound like something that can be achieved in a more sophisticated way. How?

nerd_in_rage2• 14 years ago

It's good because it's not something that should be done.

Ask yourself why you need to detect the user agent.

ricardobeat• 14 years ago

Please, let's not get started all over again. UA detection is dead. Don't do it. Mobile Safari has a zoom-in feature (double-tap) that works perfectly without any "fixes" by the website developer.

FuzzyDunlop• 14 years ago

I'd draw a distinction and say that it's probably something determined by a designer who wants to show off their Photoshop skills by having several meticulously designed websites for different devices.

As a developer, I'd leave the zoom as is and avoid this browser stuff like the plague. Too much repeated code.

ronancremin2• 14 years ago

Rumours of it's death are premature. It's used by over 80% of the Alexa top 100 sites. http://mobiforge.com/designing/blog/server-side-device-detec... Why? Because it can help tailor the user experience, reduce page payload etc.

You can test whether a site is using UA detection here: http://hydra.mobiforge.com

quarterto• 14 years ago

And billions of people smoke. Doesn't mean it's good practice.

JuDue4• 14 years ago

Hmm

I'd argue detecting iPad 2 in landscape mode would be an opportunity for an extra RHS column

While on Mini, you'd just drop that

Shame we can not have that possibility, as the extra 19% of screen makes an extra column readable.

Devilboy2• 14 years ago

I'd be pretty unhappy if my favourite website was missing a column just because I was on my mini.

JuDue4• 14 years ago

You already have that on phone vs desktop.

It's the nature of things, and should not be an issue if the responsive design is done properly

lwat• 14 years ago

Thank you Apple! Good decision there. If your site needs special tweaks just because the screen is a mere 19% smaller then your design sucks. Just my opinion.

dasil003• 14 years ago

After the ipad mini introduction video with Ive waxing on about how they redesigned it from scratch for the smaller form factor, it's irritatingly condescending that they report false results back to media queries to prevent designers from doing the same.

mikemoka• 14 years ago

would it be possible to do it by using one of these two approaches after the first general iPad user agent check?

-using a full screen image and getting an useful parameter from that via javascript

-uploading a screenshot of a graphics element via javascript/canvas for a server to evaluate

mattk4k• 14 years ago

All the comments so far have been with regards to modifying a site's appearance based on the device.

A totally separate use case is for business intelligence reporting. It's not so bad with the iPad 2 vs iPad Mini because they have virtually identical hardware other than the physical screen size (same CPU, memory, CPU, etc). However it's more important with, say, the iPad 3 vs iPad 4. Although both are fairly similar (both are branded as the "new iPad"), they do have different CPUs.

For our business, it is valuable to know which physical devices people are using, not just which OS or browser version they are on. Our product is one which heavily relies on the CPU performance - knowing which devices our customers are on tells us which devices we should prioritise the testing on. Yes, we may be able to optimise the product to work on an iPhone 3G (picked as an example of a lower end iPhone), but if the number of customers who use that device is low enough, then the business case won't stack up. When it comes to device testing, it seems only prudent to try and mimic the device profile of our customer base.

Also there are other, perhaps less tangible, use cases for understanding the device profile for our customer base. For instance, if iPad Minis are more popular for a particular demographic (perhaps rush-hour commuters), this may inform business decisions about development priorities, feature roll-out, or marketing campaigns.

In summary - please don't assume that the only reason for device detection is to change the appearance of a site; the data can be valuable in other ways too.

Tyrannosaurs• 14 years ago

I don't think anyone is assuming that that's the only reason but just because something is valuable to corporates doesn't mean you have the right to have that information.

After all I'm sure that it would be useful to you if my browser told you my age, sex, salary, where I live and how many kids I have but that doesn't mean it should happen.

Besides in this instance the hardware is remarkably similar to the iPad 2 (which is the thing you can't tell it apart from). It's unlikely there's anything the mini can do that the iPad 2 can't from a performance perspective so you really don't need to distinguish them.

JuDue4• 14 years ago

"It's not so bad with the iPad 2 vs iPad Mini because they have virtually identical hardware other than the physical screen size (same CPU, memory, CPU, etc)."

But screen size, and resulting element scaling, IS one of the most important things.

philo23• 14 years ago

This really only matters for pages designed to look "native", in which case as long as you don't have a tap area smaller than about 44x44 pixels (like Apple has always recommended) then you shouldn't really have a problem at all.

If it's a normal site then this shouldn't matter one bit because most people will be zooming into your pages anyway, unless you've disabled that (which you really shouldn't.)

No user agent detection for the iPad Mini

Related Stories