MétaCan
Menu
Back to cohort
Record W1985337187 · doi:10.1016/j.intcom.2005.01.004

Will it be a capital letter: signalling case mode in mobile phones

2005· article· en· W1985337187 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.

fundA Canadian funder is recorded on the work.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueInteracting with Computers · 2005
Typearticle
Languageen
FieldComputer Science
TopicUsability and User Interface Design
Canadian institutionsnot available
FundersYork University
KeywordsMobile deviceComputer scienceMode (computer interface)Mobile phoneHuman–computer interactionTask (project management)NotationSignallingPhoneTouchscreenText entryInterface (matter)Interaction designWorld Wide WebMultimediaTelecommunicationsEngineeringLinguisticsOperating system

Abstract

fetched live from OpenAlex

While there are well established guidelines for interaction via mouse and keyboard, new forms of interaction being devised for small handheld devices have yet to be standardised. There is a case for re-visiting basic principles for user interface design such as how to signal mode. Two ways of signalling case mode when editing text into a small handheld device such as a mobile phone are considered in this paper. One is through the system prompt, e.g. ‘Entry:’, the other is through the case of the last letter displayed in response to a button push. Two unsupervised web-based experiments are described which show that users are sensitive to both these signals for case mode. The first experiment manipulated the prompt in a text entry task using a web simulation of a novel mobile device. The results showed that users’ expectations were influenced by the case of the letters in the prompt. Users took many more trials to learn to expect a case inconsistent with the model provided by the prompt. The second experiment manipulated both the case of the letters in the prompt and the case of the last letter displayed. The results replicated the findings above and demonstrated a strong effect of the case of the last letter displayed. Guidelines for signalling case mode and a notation (Interaction Units) are suggested that might be used to reason about low level interaction design with handheld devices.

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.276
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.003
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.020
GPT teacher head0.273
Teacher spread0.252 · 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