The Code Was The Easy Part: Introducing an iOS UI Library at a Corporate
summary
Company builds an internal Swift UI library called Style Guide containing branded UIViews, UIColors and UIFonts; the proof‑of‑concept compiles in a few hours but adoption reveals testing, naming and ownership problems across a 12‑person iOS chapter. The team chooses Carthage after evaluating managers, applies semantic versioning to visual contracts (major bumps for color/typography changes), moves to modular targets, and proves weekly releases and clearer docs cut cross‑team rework and save developer hours.
AI-written summary · about
chapters (13)
- 0:00Introduction and background
- 5:15Sharing features across apps
- 7:26Target state architecture
- 8:50Building the UI component library
- 11:58Designing with best practices
- 14:47Challenges and committee lessons
- 16:32Mindset shift in teams
- 19:47Understanding team roles
- 21:14Swarming to fix the codebase
- 23:01Semantic versioning explained
- 25:50Push vs pull dependencies
- 27:36Developer experience matters
- 29:04Final thoughts and summary
related talks
18mBuckets of Code
31mMaking the Most Out of Swift
30mA Micro-services perspective on iOS architecture
42mWriting Code for Humans, Not Computers
39mThe Art of Designing Code
01h 01mGuide to Destroying Codebases the Demise of Clever Code
24mInvesting time into developer tools and experience
45mSDK Design and Publishing For Kotlin Multiplatform Mobile