MétaCan
Menu
Back to cohort
Record W2896266317 · doi:10.1109/aire.2018.00008

User Feedback from Tweets vs App Store Reviews: An Exploratory Study of Frequency, Timing and Content

2018· article· en· W2896266317 on OpenAlexaff
Gouri Deshpande, Jon Rokne

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsComputer scienceLatent Dirichlet allocationSocial mediaContext (archaeology)Feature (linguistics)Set (abstract data type)App storeSentiment analysisMobile appsWorld Wide WebTopic modelExploratory researchUser-generated contentInformation retrievalNatural language processing

Abstract

fetched live from OpenAlex

Context: User feedback on apps is essential for gauging market needs and maintaining a competitive edge in the mobile apps development industry. App Store Reviews have been a primary resource for this feedback, however, recent studies have observed that Twitter is another potentially valuable source for this information. Objective: The objective of this study is to assess user feedback from Twitter in terms of timing as well as content and compare with the App Store reviews. Method: This study employs various text analysis and Natural Language Processing methods such as semantic analysis and Latent Dirichlet Allocation (LDA) to analyze tweets and App Store Reviews. Additionally, supervised learning classifiers are used to classify them as semantically similar tweet and App Store reviews. Results: In spite of a difference in the magnitude between tweets and App Store Review counts, frequency analysis shows that bug report and feature request are discussed mostly on Twitter first as the number of Tweets during the reporting time reached the peak a few days earlier. Likewise, timing analysis on a set of 426 tweets and 2,383 reviews (which are bug reports and feature requests) show that approximately 15% appear on Twitter first. Of these 15% tweets, 72% are related to functional or behavioural aspects of the mobile app. Content analysis shows that user feedback in tweets mostly focuses on critical issues related to the feature failure and improper functionality. Conclusion: The results of this investigation show that the Twitter is not only a strong contender for useful information but also a faster source of information for mobile app improvement.

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.

How this classification was reachedexpand

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.145
Threshold uncertainty score0.447

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.001
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.110
GPT teacher head0.311
Teacher spread0.201 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations20
Published2018
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering ResearchFrench-language works237,207