Aliebelt am 3. September 2023 um 18:44 Uhr

2023-09-03T18:44:25Z

Alenz am 20. April 2022 um 06:41 Uhr

2022-04-20T06:41:13Z

Neue Seite

The recording of user interaction in emoTouch is event driven. Every time a user interacts with the interface, e.g. moves a slider, an event is triggered and recorded in the database with the exact timestamp when the event occurred. There are different kinds of events for different kinds of user interaction, e.g. slider moves, button pushes, marking checkboxes, etc. Some additional events are triggered and recorded when e.g. a part begins, a video starts playing or a user rotates his mobile device.

The event driven architecture of emoTouch stores data with the best possible time accuracy. The actual accuracy of the recorded timestamps of the events depends on various parameters, e.g. the speed of the actual device and the network connection. However, emoTouch tries to determine and compensate e.g. the network latency and stores the timestamp of an event as accurate as possible.
At the same time, the event driven architecture is very data efficient. When no interaction occurs (because e.g. the user doesn’t move a slider for a while), no events will be triggered and there will be no unneccessary network traffic and data storage.

@@ Zeile 1: / Zeile 1: @@
 The recording of user interaction in emoTouch is event driven. Every time a user interacts with the interface, e.g. moves a slider, an event is triggered and recorded in the database with the exact timestamp when the event occurred. There are different kinds of events for different kinds of user interaction, e.g. slider moves, button pushes, marking checkboxes, etc. Some additional events are triggered and recorded when e.g. a part begins, a video starts playing or a user rotates his mobile device.
 The event driven architecture of emoTouch stores data with the best possible time accuracy. The actual accuracy of the recorded timestamps of the events depends on various parameters, e.g. the speed of the actual device and the network connection. However, emoTouch tries to determine and compensate e.g. the network latency and stores the timestamp of an event as accurate as possible.
 At the same time, the event driven architecture is very data efficient. When no interaction occurs (because e.g. the user doesn’t move a slider for a while), no events will be triggered and there will be no unneccessary network traffic and data storage.

Translations:Resampling/1/en - Versionsgeschichte

Aliebelt am 3. September 2023 um 18:44 Uhr

Alenz am 20. April 2022 um 06:41 Uhr