Feature toggles with BuildConfiguration and type-safe definitions
summary
Describes using multiple Build Configurations and Swift type definitions to manage feature differences when building several iOS apps from a shared codebase (e.g., seller vs. buyer apps for a C2C service). Explains the problems with scattering #if macros—reduced readability and accidental exposure of features—and proposes leveraging type definitions to enforce feature boundaries and reduce conditional compilation sites.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:58Multi-app in one repo
- 4:33Feature toggle example
- 7:12Problems with non-type-safe toggles
- 9:23Bugs prevented by type checks
- 13:27Type definitions for safe toggles
- 15:46Dev efficiency with types
- 18:34Summary
related talks
44mFeature Toggles: The Good, The Bad, and The Ugly
41mFeature Flags: Separate Deployment from Feature Release
50mFunctional Feature Flags
51mToggle your app
27mFlag Management Techniques That Support Development of Massive Apps
39mOne Build System to Rule Them All
30mFeature toggles: ask us anything
26mMove Fast and (Don't) Break Things
