Playground Driven Development
summary
Claim: build most of the view layer inside Xcode playgrounds and shipable code lives in a framework so playgrounds import it. Tools and practices: replaced all usage of storyboards, dependency injection to isolate side effects, asset bundles per framework, and trait-override helpers to toggle size classes, languages and RTL. Examples: a Kickstarter creator dashboard per-screen playground, a counter app that calls Wolfram Alpha prime check, server‑side Swift routed responses rendered into a WKWebView. Gotchas and metrics: frequent Xcode instability (8.0–8.2 broke), advocate screenshot testing and CI compile playgrounds to catch regressions.
AI-written summary · about
chapters (4)
related talks
02h 42mSwift Structured Concurrency
54mTest Driven Development (TDD) by Controlling Dependencies
26mTesting the Tricky Stuff
38mTesting and Declarative UI's
44mHow to Stop Testing and Break Your Code Base
46mLeveraging Record and Playback for Mobile Games and XR
01h 31mAdvanced Playwright with AI
08mExample-driven development: bridging tests and documentation