The mobile industry
moves before breakfast.
So do we.
Three mobile development stories worth reading before standup — framework releases, breaking API changes, and architectural debates in Swift, Kotlin, and Flutter.
You don't need more links.
You need fewer, better ones.
The average developer newsletter sends 23 links a week. The average engineer reads three. We did the math and reversed the product. Every edition of Dispatch contains exactly three stories — chosen because they will change how you think about a decision you're making right now, not because they filled a slot.
"Curation is an act of respect for your attention."
Written by engineers shipping production code,
not content marketers skimming changelogs.
Every story in Dispatch is written by someone who has filed a crash report against the SDK being discussed, migrated a live app through the breaking change being analyzed, or argued the architectural tradeoff in a real team meeting. We don't summarize the press release. We read the diff.
"We don't summarize the press release. We read the diff."
Don't take our word for it.
Three subject lines.
Judge the density yourself.
Swift 6 Strict Concurrency: What Actually Breaks in Production
The migration guide glosses over actor isolation boundaries. We traced three real crash patterns from live apps and mapped the fixes.
Kotlin Multiplatform Hits Stable — and the Architecture Argument Starts Now
KMP 1.0 landed. The real question isn't "should we adopt it" but "where does shared code end and platform logic begin." Three teams, three answers.
Flutter's Impeller Renderer: The Benchmark Numbers Nobody Reported Correctly
The 60fps headline hides a nuanced story about memory pressure on mid-range Android. We ran the profiles. Here's what the data actually shows.
Every Wednesday's issue is publicly archived. Read last Wednesday's issue →
Get Tomorrow's
Edition.
4,200+ engineers reading daily