Warning!! New technology ahead
summary
Five practical checks — 5 diagnostic questions — decide whether to adopt SwiftUI, Combine or Swift concurrency now: would you pick it for a greenfield, what are the pitfalls, can it roll out gradually, does it fit architecture, does it solve a real problem. The recommended strategy is outside-in refactor: start at views, keep continuations bridge functions so old callbacks call through to async, keep two APIs calling one canonical logic, write tests, then deprecate old API warnings to know when to remove the bridge.
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:53Some Business don’t chase technology
- 6:175 Questions to ask to understand How do we introduce new technology
- 9:28What not to do
- 11:32Start by learning!
- 13:32Prepare your codebase for a refactor
- 16:36Where do we start?
- 20:27Having TWO version of API is great!?
- 22:43How and when do I rewrite existing code?
- 24:00Bumping iOS versions for new tech…
- 28:52It’s okay to take your time
- 30:59Summary
related talks
23mMigrating from UIKit to SwiftUI efficiently
53mRefactor Your Way Forward
37mManaging Side Effects with Swift
26mAdapting to change: design patterns in Swift
38mKeynote
40mMobiconf 2018: John Sundell, Swift by Sundell
47mHow To Build Future Proofed Applications
01h 01mGuide to Destroying Codebases the Demise of Clever Code