News for hackers. Stuff that matters.
Re:Show HN: Stop asking your clients "What browser are you on?" by rartichoke on Monday February 18, 2013 @08:24AM (#5238050)
If I'm on the phone with a client and ask them to look at something I can generally figure out what browser they have (minus the version) by asking 1 or 2 questions and that's often good enough.

Now... if you used this data in a way to automate some typical developer->client BS then I could see paying for it maybe.

For example, let's say you load up a few VMs with every major browser / browser+version combo.

Then you can tell a client to goto some url, maybe it could be something like:

http://browser.somedomain.com?for=somepage.com/preview

If the client goes to that address it captures his browser details just like your site does but then:

1. Replicates his settings with one of the VM browsers.

2. Takes a screenshot of what somepage.com/preview looks like.

3. Sends the screenshot and data to my e-mail or have an API letting me get that data back in on my end.

That has pretty high value because when a client says "the border looks weird!" that means nothing to me. I have to see the problem to be able to fix it and people who aren't technical are horrible at explaining technical problems.

Re:Show HN: Stop asking your clients "What browser are you on?" by jonasvp on Monday February 18, 2013 @08:28AM (#5238077)
I've noticed that screenshots (a la https://browsershots.org/) don't really help either as there's no way to debug - you'd change something and need another screenshot to see what happened. I guess we'll have to integrate http://browserstack.com (which is an incredible service).
Re:Show HN: Stop asking your clients "What browser are you on?" by thejosh on Monday February 18, 2013 @08:29AM (#5238084)
If you are doing that much to just see one simple page, might as well try something like browsershots.
Re:Show HN: Stop asking your clients "What browser are you on?" by rartichoke on Monday February 18, 2013 @08:35AM (#5238122)
I could but I would still have to send the client to some url to get his browser data so I know what to look up.

If I'm sending a client a url, why not take it 1 step further and eliminate any work on my end by just providing me the correct screenshot and info? Then I can shoot a client an e-mail, ask him to click a link and seconds later I'm looking at what he's looking at with his browser settings without having to do anything.