The accessibility argument is made with sufficient frequency in developer conferences and engineering blog posts that it has acquired the character of something everyone agrees with and nobody acts on. Apps ship with missing accessibility labels, unlabeled buttons, broken VoiceOver navigation, and dynamic type support that was added for text elements but forgotten for layout constraints. The gap between the accessibility investment that development teams describe as important and the accessibility state of their shipped applications is among the widest in software development.

The cross-platform vs native debate has a quality problem: the people most qualified to give objective assessments have financial or professional stakes in one answer. Agency developers who charge by the hour prefer native because it doubles the billable work. Cross-platform framework vendors publish benchmark comparisons designed to minimize the gaps between their output and native. Native platform advocates at Apple and Google have obvious incentives to characterize cross-platform output as inferior.

Mobile security vulnerabilities cluster in a predictable set of categories. The same mistakes appear in security audits of consumer apps, enterprise apps, and fintech apps with equal regularity. The recurrence of the same errors across different teams and different organizations suggests that the failures are not primarily due to ignorance — most mobile developers are aware that security matters — but to a gap between security knowledge and the specific engineering practices that translate that knowledge into secure code.

SwiftUI launched in 2019 with a demonstration that made experienced iOS developers simultaneously excited and nervous. Excited because the declarative paradigm promised to eliminate the impedance mismatch between interface builder storyboards and code. Nervous because Apple’s track record with new frameworks included several that were replaced, deprecated, or quietly ignored within a few development cycles.

Five years later, SwiftUI is neither the complete replacement for UIKit that Apple’s marketing implied nor the abandoned experiment that skeptics predicted. It is a mature but still-evolving framework that handles a large majority of common iOS UI requirements elegantly, struggles with a specific set of advanced requirements, and has permanently changed how iOS UI code is written even when developers reach for UIKit to solve problems SwiftUI cannot.

The question of whether to build natively for iOS and Android or to abstract across both platforms with a cross-platform framework has occupied mobile development teams for more than a decade. The answer has not settled. What has settled is the character of native development itself — and in 2026, Swift and Kotlin have each reached a maturity that makes the native argument significantly stronger than it was five years ago.