Claims

Students developed mobile CT concepts, practices, and perspectives through app development activities

Claim · All claims
Evidence · 1 study · design r2 · q2
Currency · newest study 2025 · not yet checked against its sources · not reviewed by a person

Subclaims

Reading the evidence codes

q is the design tier, i the impact, n the sample, and the kind with its r the rigour judged within that kind: what each code means.

This claim: no standardized effect is recorded in observations/ for it yet, so no benchmark reading is possible.

q2 i? Teacher interviews indicated students used App Inventor components, sequences, loops, conditionals, and data persistence, and applied mobile CT practices including modeling, testing and debugging, and reusing and remixing. → Fang 2025

Evidence

Fang 2025

Fang, X., Ng, D. T. K., Tam, W. T., & Yuen, M. (2025). Design mobile computational thinking-integrated mathematics lessons based on the 5E instructional model for primary students. Education Tech Research Dev. https://doi.org/10.1007/s11423-025-10513-x

q2 · i? · design · r2

Post-lesson interviews with the teacher and teacher assistants about students' mobile CT development. The teacher reported students used components like 'buttons, text boxes, GPS, sound player to design app interfaces' and saved designs to the App Inventor data server.

"Students could use sequences and loops to identify and repeat their game by clicking “restart”, conditionals to make decisions to handle different conditions and cases."

Discussion

Page metadata
Field Value
type claim
id students-developed-mobile-ct-competencies
title Students developed mobile CT concepts, practices, and perspectives through app development activities
description Students developed mobile CT concepts, practices, and perspectives through app development activities
status review
evidence_strength moderate
newest_evidence 2025
generated by process:wiki-ingest on 2026-10-29
trust unverified — no one has confirmed this page's content
sources 1 — fang-2025

Frontmatter is the page's machine-readable record — see the Schema & Guide.