Jesus Perez Mojica: Why Apple Is Secretly Betting Against Native iOS Development
Original post Why Apple Is Secretly Betting Against Native iOS Development
Article Summary
Apple is quietly pushing developers away from the native iOS stack they've championed for over a decade. The evidence? Look at what they're building, not what they're saying.
This analysis examines Apple's recent strategic moves that suggest a fundamental shift in their development philosophy. Despite publicly promoting Swift and native iOS development, their actions tell a different story about the future of app development on their platforms.
Key Takeaways
- Apple's own apps increasingly use web technologies and cross-platform frameworks internally
- SwiftUI adoption remains slow even within Apple, with UIKit still dominating
- App Store guidelines now favor progressive web apps with new capabilities
- Apple invested heavily in WebKit performance while native tools stagnate
- Cross-platform frameworks get preferential treatment in App Store review times
Apple's investment patterns and internal practices reveal a strategic pivot toward web and cross-platform technologies, contradicting their public native development messaging.
Continue reading
What This Article Covers
Apple needed to get Swift running on more than just iOS. The language needed official support for Android and WebAssembly as first-class targets.
Jesus Perez Mojica documented how Apple added Swift 6.1 WebAssembly as Tier-1 support and created an Android Workgroup at Swift.org. This let Swift compile to wasm32-unknown-wasi and produce Android-compatible binaries directly.
Swift stopped being Apple-only and became a portable systems language. Developers can now share core logic across iOS, Android, browsers, and serverless environments using a single codebase.
This page summarizes “Why Apple Is Secretly Betting Against Native iOS Development” by Jesus Perez Mojica, published Feb 15, 2026. All credit for the original work goes to the authors.
