@article{BorchertSeufertGamboaetal.2020,
  author    = {Borchert, Kathrin and Seufert, Anika and Gamboa, Edwin and Hirth, Matthias and Hoßfeld, Tobias},
  title     = {In Vitro vs In Vivo: Does the Study's Interface Design Influence Crowdsourced Video QoE?},
  series = {Quality and User Experience},
  volume    = {6},
  journal   = {Quality and User Experience},
  issn      = {2366-0139},
  doi       = {10.1007/s41233-020-00041-2},
  url       = {http://nbn-resolving.de/urn:nbn:de:bvb:20-opus-235586},
  year      = {2020},
  abstract  = {Evaluating the Quality of Experience (QoE) of video streaming and its influence factors has become paramount for streaming providers, as they want to maintain high satisfaction for their customers. In this context, crowdsourced user studies became a valuable tool to evaluate different factors which can affect the perceived user experience on a large scale. In general, most of these crowdsourcing studies either use, what we refer to, as an in vivo or an in vitro interface design. In vivo design means that the study participant has to rate the QoE of a video that is embedded in an application similar to a real streaming service, e.g., YouTube or Netflix. In vitro design refers to a setting, in which the video stream is separated from a specific service and thus, the video plays on a plain background. Although these interface designs vary widely, the results are often compared and generalized. In this work, we use a crowdsourcing study to investigate the influence of three interface design alternatives, an in vitro and two in vivo designs with different levels of interactiveness, on the perceived video QoE. Contrary to our expectations, the results indicate that there is no significant influence of the study's interface design in general on the video experience. Furthermore, we found that the in vivo design does not reduce the test takers' attentiveness. However, we observed that participants who interacted with the test interface reported a higher video QoE than other groups.},
  language  = {en}
}