As briefly discussed yesterday, unless you have a better idea, it might make sense to log a few key events in a separte table usage_data with the columns id, ts (or created, edited, ...), type and additionalInformation:
The idea of additionalInformation is to flexibly add extra context/data, where useful. In past studies, we sometimes added json objects that we could later easily parse.
The following event-types (for now):
[x] start (app start, also log timezone and app version number)
[x] stop (app shutdown)
[x] lock-screen (logout/signout/lockscreen)
[x] unlock-screen
[x] startExport
[x] finishExport (+ settings)
[x] opened + closed/answered experience sampling popup and wheter it was automated or manually opened
As briefly discussed yesterday, unless you have a better idea, it might make sense to log a few key events in a separte table
usage_datawith the columnsid,ts(or created, edited, ...),typeandadditionalInformation:The idea of additionalInformation is to flexibly add extra context/data, where useful. In past studies, we sometimes added json objects that we could later easily parse.
The following event-types (for now):