The Layout Framework
summary
A framework that loads runtime-evaluated XML files to build iOS screens, acting as a drop-in replacement for nibs (one XML file per screen) and using an expressions library to compute layout values at runtime (no JavaScript, pure Swift evaluation). It supports live simulator reloads, localization lookup, template composition and parameter passing, shows a red box error screen instead of crashing on type or binding errors, and runs in production in 3–4 apps with Apple approvals.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:12MULTIPLE DEVICES SIZES MULTIPLE LANGUAGES/LOCALES DESIGN TOOLS ARE UNLIKE DEV TOOLS
- 1:31APPLE'S SOLUTION: STORYBOARDS AUTOLAYOUT
- 3:03BAD: OPAQUE, PROPRIETARY FORMAT HARD TO COLLABORATE LIMITED REUSABILITY HARD TO REFACTOR HARD TO INJECT CONSTANTS
- 4:57ALTERNATIVES: LAYOUT IN CODE 3RD PARTY TOOLS (React Native?)
- 6:11COMPLICATED (steep difficulty curve) SLOW / UNBOUNDED (recursive) HARD TO REASON ABOUT (weights) HARD TO CHANGE (constraint spaghetti)
- 9:36EXPRESSIONS ARE: RUN-TIME CODE EVALUATION WITHOUT JAVASCRIPT/GC
- 28:41HELPFUL ERROR MESSAGES TEMPLATES AND PARAMETERS LOCALIZATION AND ACCESSIBILITY OTA UPDATES
- 29:30WORKS WITH NATIVE CODEBASE WORKS WITH EXISTING COMPONENTS








