Many apps skip new platform APIs

Bastien Gares wrote in an August 2026 X post that many large consumer apps on Android still ship interfaces that ignore recent platform APIs and design conventions, reviving a familiar complaint inside mobile development circles. The post focused on visible mismatches — older controls, outdated navigation patterns and inconsistent styling inside otherwise current apps. Official documentation from Google, Apple and cross-platform framework vendors shows why that gap persists: modern platform design systems exist, but adopting them often requires explicit migration work, platform-specific code and coordination across design and engineering teams. ### Why do newer platform features get skipped in the first place? Flutter says developers can ship “multi-platform applications from a single codebase,” but its own platform integration guide says teams still “occasionally” need platform-specific functionality and may have to write custom code or plugins. The same guide points developers to Android-specific integrations such as calling Jetpack APIs, embedding Android views and launching a Compose activity from Dart. (developer.android.com) Flutter’s adaptive design documentation draws a sharper line. The company says some operating-system behaviors adapt automatically, but app-level design choices often do not. For conventions typically implemented with an OEM’s SDK, Flutter says it provides the tools to build the right behavior but “doesn't adapt automatically when app design choices are needed.” React Native makes a similar point in plainer terms. (docs.flutter.dev) Its documentation says developers building cross-platform apps may need separate visual components for Android and iOS, and it offers platform detection, platform-specific file extensions and native modules to do that work. Its native modules guide says mobile features often require direct use of Android and iOS APIs. ### What do Google and Apple say apps should be using now? (docs.flutter.dev) Google’s Android documentation says Material Design 3 is “the latest iteration” of Material Design, and its Compose guidance says Material 3 includes updated theming, components and Material You personalization features. A migration guide published this month says teams should ideally start moving from Material 2 to Material 3 “as soon as possible.” (reactnative.dev) The same Android migration guide warns against running Material 2 and Material 3 together for the long term because the systems differ significantly in design and implementation. Google says teams should take a phased approach and, if necessary, carry old and new systems side by side while they move components over. Apple’s Human Interface Guidelines tell developers to “adopt platform conventions” to maintain consistency across devices and displays. (developer.android.com) Apple’s SwiftUI materials from WWDC 2025 say developers can give apps a “brand new look and feel” with Liquid Glass and other framework updates, while Apple also says SwiftUI can be adopted incrementally alongside UIKit. ### Why do users notice this more on Android? Google’s Android 16 documentation says the platform adds new capabilities for “beautiful apps” and calls on developers to test, update and target Android 16 where possible. (developer.android.com) Google’s developer materials in recent weeks have also highlighted Material 3 Expressive and Android 16 together, linking design changes to newer system UI. That means older interface layers can stand out more clearly when an app mixes new system surfaces with older in-app components. (developer.apple.com) Google’s migration guide says Material 2 and Material 3 differ significantly enough that long-term mixing is not recommended. ### Is this mainly a cross-platform problem? React Native’s homepage still describes the framework as a way to build native apps for Android, iOS and more using React, and Flutter markets a single codebase across platforms. (developer.android.com) Those promises reduce duplicate work, but both toolchains also document the need for platform-specific branches when native behavior or native presentation matters. Google and Apple do not describe that trade-off as a flaw. Their documentation instead treats migration as an ongoing process: Android says to target Android 16 if possible and test on beta channels, while Apple continues to publish updated Human Interface Guidelines and SwiftUI sessions for each release cycle. (developer.android.com) Teams that want current-looking apps have those references now, and both platform owners are still adding new APIs and design guidance ahead of their next developer events. (developer.android.com) (reactnative.dev)