DartNative Swaps Flutter's Rendering Engine for UIKit and Android Views
DartNative surfaces a real pain point: Flutter's rendering abstraction still introduces frame-level lag in interactions like keyboard avoidance and video transitions. A framework that compiles Dart to native views offers a concrete benchmark for what Flutter itself leaves on the table.
A new project called DartNative compiles Dart code directly to native rendering, using UIKit on iOS and Android Views on Android instead of Flutter's Skia-based engine. It claims zero abstraction layers and no bridge, positioning itself as a direct-to-native alternative for developers who want to keep writing Dart but are unhappy with Flutter's rendering performance.
The framework's pitch centers on scenario-specific optimizations that are hard to achieve in Flutter. Keyboard animations sync with the system's Core Animation transaction on iOS and WindowInsetsAnimation on Android, shaving frames off the typical Flutter keyboard experience. Long lists, video playback, and WebView all receive similar native-level tuning, including a video player with built-in pre-caching for zero-delay transitions.
Despite the technical ambition, the plugin ecosystem is thin — only 34 first-party plugins exist — making migration from Flutter painful. The project appears aimed at a narrow slice of Flutter developers frustrated with specific interaction bottlenecks, but the author notes that even the community fork Flocker has already adopted more modern rendering paths like Graphite.
Launching a new cross-platform framework in 2026 to siphon off Flutter users is an odd bet — the window for framework fragmentation closed years ago, and the plugin gap alone makes migration a non-starter for most teams.
DartNative's real value isn't as a Flutter replacement but as a stress test: it demonstrates exactly which interactions Flutter's engine still can't handle natively, and those gaps are measurable in frames.
The project's existence suggests a small but persistent group of Dart developers would rather switch rendering backends than abandon the language, which says more about Dart's stickiness than Flutter's weaknesses.
The discussion centers on DartNative's practical role. One view holds that full replacement of Flutter is unrealistic, but the framework could shine as a drop-in fix for Platform View's notorious Android overhead. A separate question asks whether the earlier Flocker project has already been abandoned, and a final remark attributes the entire shift to AI taking over development work.
Replacing Flutter isn't very realistic, but it would be nice as a supplement to Flutter. If this approach could replace Flutter's Platform View, that would be great — the overhead of Platform View is still quite noticeable, especially on Android.