How AI tipped the scales from cross-platform to native mobile development

Shopify's decision to abandon React Native for its flagship apps in favor of Swift and Kotlin is the kind of news that forces a long, hard look at assumptions we've all been carrying. For years, the conventional wisdom held that cross-platform frameworks were the only sane way to manage mobile development at scale. The math was simple: one codebase, two platforms, lower cost. But Mustafa Ali, Shopify's Head of Mobile, has publicly stated that the quality of AI models has shifted that equation. The benefit/cost ratio of maintaining native codebases, he argues, has now tipped past the abstraction layer's advantages. That is not a casual observation. It is a direct challenge to the foundational logic that has guided countless architecture decisions since React Native first gained traction. We think this is a moment worth pausing on, not because Shopify is the first company to walk back a cross-platform bet, but because the stated reasoning is so clear-eyed about *why* the calculus changed. AI is not just automating boilerplate code generation; it is compressing the maintenance burden that once made native development prohibitively expensive. When AI assistants can scaffold Swift and Kotlin code with increasing reliability, the primary cost of going native, the duplicated effort across two codebases, starts to evaporate. What remains is the performance, the platform-specific polish, and the deep integration that users have always expected but that we were willing to sacrifice for the sake of speed. The tradeoff is no longer what it used to be, and pretending otherwise is a risk. This connects to a broader tension we are seeing play out across the industry, one that is also visible in the Zig’s Creator Explains AI Ban and Shift to Codeberg for Quality and Community story, where a different kind of line is being drawn around AI's role in a codebase. Here, it is about letting AI change the cost structure; there, it is about banning it entirely to protect quality. Both are reactions to the same underlying force, but they could not be more different in their conclusions. For our readers, the practical takeaway is not that you should immediately rewrite your mobile apps. That would be a misreading. The real insight is that your technology choices are not permanent monuments; they are bets on a set of conditions that can change. The conditions have changed. AI has not made cross-platform frameworks obsolete, but it has changed the price of admission for native development. If you have been holding off on a native feature because of cost, or if you have been frustrated by the limits of a shared abstraction layer, this is the moment to re-run the numbers. We would tell a reader who asked us directly: do not just look at your current team's comfort with React Native. Look at what AI tools can do for you today. The gap between what a small team can maintain natively and what used to require a cross-platform framework is narrowing, and it is narrowing faster than most budgeting cycles account for. The question that lingers, and the one we will be watching, is how this plays out in the long tail. Shopify's move is a strong signal, but it is also a bet on a specific trajectory of AI capability. We would caution against assuming that what works for a company with Shopify's engineering resources will automatically translate to a five-person startup. The costs of native development are not just about writing code; they are about expertise, hiring, and long-term maintenance. AI can lower the barrier, but it does not erase the need for specialized knowledge. The real test will come in the next eighteen months, as other large teams decide whether they see the same math. We would rather see engineering leaders make this call based on their own metrics, not on momentum or fear of missing out. The specific detail to watch is how quickly AI-assisted native development closes the remaining feature gap. If that gap closes, the abstraction layer's days are numbered. If it stalls, then this will be remembered as a bold but isolated move. Either way, the default assumption that cross-platform is the only rational choice is gone.