Shopify is moving every mobile app off React Native to Swift and Kotlin, with its Shop app in stores 12 weeks after a one-week agent-built prototype. The shipped app came out of a gated, screen-by-screen review process that a team copying Shopify would have to build first.
Reality
- Evidence40
- Adoption30
- Hype gap+10
- Incentives
- Insufficient
- Confidence45
Open Food Facts replies to an unknown barcode with HTTP 404 and a product-not-found body. SnapCal's 200-to-299 guard threw before anything read that body, so the commonest outcome reached users as "Server error (404)".
Reality
- Evidence60
- Adoption15
- Hype gap0
- Incentives50
- Confidence62
Shopify is dropping React Native five years after standardising on it, on Head of Mobile Mustafa Ali's estimate that two native codebases now beat a shared runtime. Its reported gains compare against React Native's old architecture.
Reality
- Evidence45
- Adoption45
- Hype gap+20
- Incentives65
- Confidence55
Shopify's case for dropping React Native rests on agents porting features between iOS and Android. The tooling built around those agents shows how much human review that still takes, and what the switch costs in hotfix speed.
Reality
- Evidence32
- Adoption40
- Hype gap+35
- Incentives62
- Confidence40
A menu bar copy of the iPhone Duo status ring went on sale two days after Apple showed it, and the day that was not spent writing Swift went to certificates, license keys, self-update and one permission prompt the app declines to trigger.
Reality
- Evidence52
- Adoption18
- Hype gap+6
- Incentives45
- Confidence55
The merged PR shares source, resources and themes with the phone build while keeping storage separate, and on Android the standalone flag takes the phone product's slot because no companion Wear APK exists yet.
Reality
- Evidence46
- Adoption12
- Hype gap−6
- Incentives74
- Confidence45
Linking generated Swift against a reimplemented framework buys a local browser preview and an Android build from one source, which leaves Dactyl owning parity with frameworks it does not control. Agents do that work now.
Reality
- Evidence44
- Adoption22
- Hype gap+26
- Incentives71
- Confidence49
A practitioner post argues a server buys a two-person iOS app nothing. It also, without saying so, trades four operational costs for four client-side correctness problems.
Reality
- Evidence44
- Adoption
- Insufficient
- Hype gap+27
- Incentives31
- Confidence41
A workout app recomputes every coaching verdict from raw logs. That stayed affordable only after seven tables got indices, and the observability added to prove it had been dropping every span.
Reality
- Evidence44
- Adoption11
- Hype gap+9
- Incentives71
- Confidence37
One iOS team's own measurement puts the value of agent workflows in the mechanical half of code review. In Swift, letting agents generate freely moved the time the other way.
Reality
- Evidence24
- Adoption20
- Hype gap+9
- Incentives55
- Confidence41
A dev.to post pins down a refactor most teams mislabel: only a separate View type adds a node with its own identity and dependencies. Computed properties move text around.
Reality
- Evidence48
- Adoption
- Insufficient
- Hype gap−8
- Incentives22
- Confidence44
A developer shipped Mathastic as separate SwiftUI and Compose apps, keeping nine domain types in common and letting the implementations diverge. The discipline sits in the vocabulary, not the code.
Reality
- Evidence32
- Adoption8
- Hype gap+12
- Incentives62
- Confidence34
A developer set Dynamic Type to the largest size, screenshotted every screen, and surfaced the same layout defect eleven times. In Japanese it fails much earlier than in English.
Reality
- Evidence44
- Adoption
- Insufficient
- Hype gap+14
- Incentives55
- Confidence45