State of the art in browser capability detection
State of the art in browser capability detection
- Subject: State of the art in browser capability detection
- From: Paul Hoadley <email@hidden>
- Date: Wed, 15 Oct 2014 10:57:47 +1030
| Hello,
I am interested to know what people are doing in practice to detect browser capabilities and serve up different page-level components, specifically for mobile devices.
I have a particular project for which the mobile front end is a small subset of the views available on the desktop. It's not suitable for the kind of "responsive design" where we would let the UI degrade gracefully on the client side. Take it as read that we can't do that at the moment, and I need to serve specific page-level components for "mobile devices" (which I'll deliberately leave poorly defined). Ideally I'd like to do this from first page load—the user should get a mobile-specific login page—so any solution that included client-side capability detection would need to take that into account.
I'm happy to use the kind of UA string sniffing technique employed by ERXBasicBrowser (and have employed exactly this in other projects), thought that class doesn't seem to have seen much love lately, and I suspect it's a bit out of date. I'm keen to know if the state of the art has moved on.
Can anyone take 5 minutes to describe, even just broadly, any techniques they're using to solve this kind of problem in the real world?
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden