Apple's Swift Playgrounds for iPad is designed for kids but still requires coding, doesn't generate standalone apps
Adam Banks / Ars Technica UK : Tweets: @jamiebullock Tweets: Jamie Bullock / @jamiebullock : “HyperCard succeeded precisely because it didn't try to teach anyone to be a programmer” http://arstechnica.com/...
Context & Ripple Effects
A month after Apple unveiled Swift Playgrounds as a free fall release for teaching kids programming concepts (the June announcement), Ars Technica's Adam Banks is drawing the line between what it promises and what it delivers: learners still write real code, and nothing they build leaves the app as a standalone program. The sharpest critique comes from Jamie Bullock, who points to HyperCard — Apple's own classic — arguing it succeeded precisely because it didn't try to turn users into programmers.
First-order effects
- Kids and educators get a polished Swift-learning environment whose output stays trapped inside the playground — no shareable or installable artifact, which limits its use beyond guided lessons.
Second-order effects
- The 'teaches coding but ships nothing' gap creates obvious pressure on Apple to close it — a gap the company eventually filled when Swift Playgrounds 4 let users develop apps on iPad and upload them straight to the App Store.
Third-order effects
- If the arc from lesson-sandbox to real app pipeline holds, the iPad consolidates as a creation device in its own right — reinforced by the shared-architecture path Apple later opened when Apple-silicon Macs could natively run iOS apps, blurring where apps are made versus where they run.
The trend: Learn-to-code tools are evolving from isolated teaching sandboxes into genuine on-device development pipelines, with Apple's own HyperCard legacy setting the bar for programming-free creation.