Let’s make your DATA sexy
summary
Covers hands‑on advice for treating API payloads as first‑class design: practical comparisons of parsers and performance tradeoffs (mentions Swift Codable and alternatives), use of Moya and stub/recorded responses for offline testing, cache‑policy pitfalls, explicit UI state machines instead of ad hoc flags, migration and dependency risks during Swift upgrades, and concrete error‑handling patterns including silent retries and cached fallbacks. Examples include profiler‑style benchmarks, migration anecdotes, and small code patterns that were tested for real.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:31Bear
- 3:29Jason
- 5:46JSON
- 11:06Software Houses
- 14:39Risk
- 16:38Swift Migration
- 22:33Handling States
- 24:41Explicit States
- 25:52Offline States
- 28:56Passing the data
- 31:21Handling errors properly
related talks
55mEmerging Best Practices
47mAdvanced Codable — When the API wasn’t built for Swift
50mWriting Swift code with great testability
30mLeveraging Swift's Type System
37mWhy to Use Design First and Server Side Swift if Everything Works Anyway
48mLearning From Our Elders: Applying functional insights without losing Swift
18mSilver Bullets in Swift
31mMaking the Most Out of Swift