Teacher app builders need handoffs teachers can inspect
A teacher’s prompt does not become an app in one jump. It becomes a plan, package, checks, fixes, and approval state. Each handoff can change the learning goal. Teachers need readable evidence of what changed, and a way to object.
What the source reports
This paper studies Studio, a teacher tool that turns plain English class briefs into app packages. The authors review six eligible attempts across three accounts. They also use a separate public workshop set of 37 idea units. The abstract says two drafts met package and security checks despite review concerns and loose fit to the brief. Four attempts in one account produced no usable payload. Repair messages used internal system terms instead of fixes teachers could read. The authors call the answer accountable translation. That means changes should have owners, be easy to inspect, be checked against a clear scope, and allow objections. This is a small workshop record, not classroom proof.
Original source
- Title
- Beyond Prompt-to-App: Accountable Translation in Teacher-Facing Agentic Authoring
- Author
- Kadir, Liow, Khan & Ang
- Publication
- arXiv
- Date
- Friday, September 4, 2026