MétaCan
Menu
Back to cohort
Record W4391509231 · doi:10.1093/iwc/iwae001

Identifying the Importance of UX Dimensions for Different Software Product Categories

2023· article· en· W4391509231 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
fundA Canadian funder is recorded on the work.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueInteracting with Computers · 2023
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsPolytechnique Montréal
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsComputer scienceProduct (mathematics)SoftwareHuman–computer interactionSoftware engineeringProgramming languageMathematics

Abstract

fetched live from OpenAlex

Abstract Billions of users around the world use mobile applications and computer software to achieve their professional and personal goals. This situation drives User Experience (UX) researchers and practitioners to assess the importance of UX dimensions across different products, to facilitate the design, development and evaluation of new products. To that end, this study surveyed a group of 200 end users and 8 UX experts from Canada to document the importance of 21 UX dimensions for 15 software product categories. The results confirmed that the importance of UX dimensions varies between product categories. Comparing the findings to those of similar studies conducted in Germany and Indonesia revealed that, while culture influences the rating of UX dimensions, the importance of UX dimensions is still determined by the product category. Comparisons between the importance ratings of UX dimensions between end users and experts and within end users were not significant in 77% and 97% of cases, respectively. Results showed that task-based product categories rely more on pragmatic dimensions (i.e. functionality and usability) while leisure-based products value hedonic dimensions (i.e. pleasure) as well. This study benefits researchers and practitioners by enabling them to select the most important UX dimensions for evaluating their products. CCS CONCEPTS: • Human-centered computing • Human-Computer Interaction (HCI) • HCI design and evaluation methods. Additional Keywords and Phrases: User experience, UX dimension, UX evaluation, culture.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.666
Threshold uncertainty score0.390

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.034
GPT teacher head0.298
Teacher spread0.264 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it