Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Query participant's device
#1
Is there any way to query the participant's device? For example, can we play audio and automatically determine whether they used headphones or computer speakers? Or can we automatically determine whether they used a touchpad, touchscreen, or external mouse to respond?
Reply
#2
This is a good question, and the answer is a bit complex. There is some information that we can get: what browsers they are using, what the screen resolution is, and what the participant's local time is, etc. However, most hardware specs, like those you listed, are not (yet). This is because modern browsers are treated as "sandboxes" for security reasons. Google, Mozilla, Microsoft, etc purposefully hide hardware-level information from web apps to prevent malicious actions that a rogue app may take.

That being said, Google is working on a proprietary API that will expose more hardware details. This is unfortunately a controversial plan and opposed by many in the field, for very good reasons. We are monitoring these developments.

In other words, unfortunately, such hardware-level information cannot be obtained at the time being. Sorry for the disappointing news.
Reply
#3
(02-10-2021, 10:32 PM)Has this changed in the interval since you posted this answer, Ting? I am working on a mouse-tracking study, and when my collaborator wanted to test it out, she got the message that 'This study requires an external mouse, please connect one and refresh your browser'.I am wondering two things:1. My collaborator in fact IS using an external mouse. It's wireless, but presumably that doesn't matter? Why might she be getting that message?2. Can this requirement be turned off? Does mousetracking not work with built-in trackpads etc? Thanks!Ting Wrote: This is a good question, and the answer is a bit complex. There is some information that we can get: what browsers they are using, what the screen resolution is, and what the participant's local time is, etc. However, most hardware specs, like those you listed, are not (yet). This is because modern browsers are treated as "sandboxes" for security reasons. Google, Mozilla, Microsoft, etc purposefully hide hardware-level information from web apps to prevent malicious actions that a rogue app may take.

That being said, Google is working on a proprietary API that will expose more hardware details. This is unfortunately a controversial plan and opposed by many in the field, for very good reasons. We are monitoring these developments.

In other words, unfortunately, such hardware-level information cannot be obtained at the time being. Sorry for the disappointing news.
Reply
#4
What's the device and operating system that your collaborator is using? It doesn't matter whether the mouse is wireless or wired, but if the device is touch-primary (as it self-declares), then you'll see the message unfortunately. For example, an iPad may do that, also some other touch-capable devices (but not all).

We don't think we'd like to remove this detection mechanism, because, as a whole, it very effectively prevents participants from not following directions. In a sense, what your collaborator experienced is a good thing - we want to make sure that not only a mouse is present, it's also IMPOSSIBLE to use touch at the same time. Because participants, when given the convenience of touch, will touch instead of using a mouse in most cases.

As a platform, we'd rather introduce the inconvenience of asking the participants to use a different device, rather than researchers finding missing mouse tracking data after the fact (although some marginal cases may still slip through). Wink

Hope this helps!
Reply
#5
(04-12-2022, 04:50 PM)Thanks for clarifying. The strange thing is that my collaborator was using a computer with an external mouse connected. Any idea why the message appears in this context?Ting Wrote: What's the device and operating system that your collaborator is using? It doesn't matter whether the mouse is wireless or wired, but if the device is touch-primary (as it self-declares), then you'll see the message unfortunately. For example, an iPad may do that, also some other touch-capable devices (but not all).

We don't think we'd like to remove this detection mechanism, because, as a whole, it very effectively prevents participants from not following directions. In a sense, what your collaborator experienced is a good thing - we want to make sure that not only a mouse is present, it's also IMPOSSIBLE to use touch at the same time. Because participants, when given the convenience of touch, will touch instead of using a mouse in most cases.

As a platform, we'd rather introduce the inconvenience of asking the participants to use a different device, rather than researchers finding missing mouse tracking data after the fact (although some marginal cases may still slip through). Wink

Hope this helps!
Reply
#6
Outdated browser version? This seems to be an idiosyncratic issue. Our mousetracking template study seems to be working fine.

If you can provide the device, operating system, browser and its version, we can try to replicate this issue on our end.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)