• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: State of the art in browser capability detection
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: State of the art in browser capability detection


  • Subject: Re: State of the art in browser capability detection
  • From: David Holt <email@hidden>
  • Date: Tue, 14 Oct 2014 17:55:34 -0700

Hi Paul,

We're beginning to tackle just this problem. One helpful site is http://www.whatismybrowser.com and has an API available, but I'm not sure that it does anything different than you could do in WO. We use it in a support context to tell people whether they are running a browser considered out of date and gives instructions for how to update, turn on _javascript_ etc. I've realized since, though that it is quite laptop/desktop centric since a quick download will not be the solution to upgrade a browser on mobile devices. 

Another problem we're encountering is the huge variety in connection speed differences between "modern" devices. Also, since people are now using USB cel sticks or their mobile devices as hotspots for laptops, the variety is unpredictable and vast. We can no longer make the assumptions about connection speed that we could have even a couple of years ago.

Sorry for no solution, but maybe our experience can add fuel to the fire :)

David

Sent from my iPad

On Oct 14, 2014, at 5:27 PM, Paul Hoadley <email@hidden> wrote:

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?


-- 
Paul Hoadley
http://logicsquad.net/

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
  • Follow-Ups:
    • Re: State of the art in browser capability detection
      • From: Paul Hoadley <email@hidden>
References: 
 >State of the art in browser capability detection (From: Paul Hoadley <email@hidden>)

  • Prev by Date: State of the art in browser capability detection
  • Next by Date: Re: State of the art in browser capability detection
  • Previous by thread: State of the art in browser capability detection
  • Next by thread: Re: State of the art in browser capability detection
  • Index(es):
    • Date
    • Thread