🧙 Wiz Kids
LearnDesign Memos

Design memo: why Wiz Kids requires a real keyboard

Design memos document real decisions in Wiz Kids and the research behind them.

Before a child's first lesson, Wiz Kids runs a "cockpit check": power up your wand by pressing a two-key chord. No chord, no lessons — a tablet without a keyboard gets a deliberately limited away mode (review quizzes, safety scenarios, the shop) instead of the curriculum. In an edtech market that prizes works-on-everything, requiring hardware is a strange flex. This memo is the reasoning.

The curriculum is motor, so the hardware is the content

A large fraction of what we teach is motor skill on specific hardware: touch typing, chords and caret navigation, precision mouse/trackpad work. On a glass screen these lessons aren't harder — they're counterfeit: "typing" on glass practices a different skill with different motor programs (automatization is indiscriminate — it compiles whatever is practiced, including tap-typing), and a shortcut "taught" without keys is a fact about a skill, not the skill. Allowing the full curriculum on keyboardless devices wouldn't widen access to it; it would quietly substitute a different, lesser curriculum while reporting the same completion metrics. The requirement is honesty about what's being learned.

Capability, never device

The line we drew carefully: the gate tests capability, not identity. We detect nothing about the device model and blocklist nothing — an iPad with a keyboard passes the cockpit check fair and square, because the chord is the test and the chord is the point. This matters doubly: device blocklists rot (new hardware, hybrids, whatever ships next year), and identity-based gating punishes exactly the resourceful setups (the tablet-plus-cheap-keyboard family) that deserve to work. One chord, pressed, settles the only question we have.

The equity objection, taken seriously

The hard objection: keyboards correlate with resources — doesn't the requirement exclude the children the access gradient already disadvantages? We weighed this heavily, and concluded the requirement runs the other way, for two reasons. First, our deployment model is classroom-first: school machines have keyboards; home access is a bonus lane, never load-bearing — so the child with only a family tablet is not locked out of the curriculum; they do it at school, like the model assumes. Second, the alternative — a glass-compatible "typing" curriculum — would deliver the inequity it claims to avoid: affluent children would still learn real typing (on the home laptop), while tablet-only children received the counterfeit and a certificate saying otherwise. Away mode is the honest middle: real value on glass (judgment scenarios, reviews, safety content — things glass teaches truthfully), clearly framed as away, with the fiction saying why: "lessons need a real computer with a keyboard."

The gate as first lesson

A quiet bonus we've come to value: the cockpit check is the product's first interaction, and it teaches — the chord is a real chord (the power-up gesture is literally shortcut practice), the pointer question ("mouse or trackpad?") starts the machine-awareness thread, and the framing installs the identity we want: you are the operator of this machine; prove the controls work. Diegetic gating beats error messages.

References


© Glu IO Pty. Ltd. — Wiz Kids (wiz.kids). Link freely; republication requires permission — see terms. Found an error in our reading of the research? We correct fast: tell any teacher piloting Wiz Kids.