02 / 23
Building the same feature in Swift and Kotlin no longer carries the cost it used to.
— Mustafa Ali, Shopify Engineering
04 / 23
If AI can write Swift and Kotlin for you, why use cross-platform at all—including Flutter?
Worried Dash surrounded by AI robotic arms
05 / 23
CORE THESIS

Flutter Owns the Pixels in One Codebase.

01 · GPU Pixel Ownership
  • • Renders custom pixels on the GPU
  • • Ships core visuals inside one SDK
02 · Zero-Drift Workflow
  • • Prevents platform drift with one codebase
06 / 23
ENGINE & DEPENDENCIES

Flutter Ships Heavy Visuals in the SDK.

01
SliverList
02
Animations
03
Impeller GLSL
3D
Flutter GPU + Stac
  • • React Native needs external UI packages
  • • Flutter SDK bundles lists, animations, shaders
  • • One SDK upgrade advances every visual
07 / 23
PERFORMANCE VS. EFFORT · 120 FPS = 8.3 MS

Extra Native Headroom Beyond 120fps Is Invisible.

Flutter (1 Codebase) 120 FPS (8.3 ms)
Pure Native (2 Codebases) 120 FPS + Unseen Headroom
  • • Impeller hits 120fps within 8.3ms frames
  • • Unused CPU headroom is invisible onscreen
10 / 23
FULL SDLC · SOURCES: IEEE TSE · IDC · BROOKS · DORA

AI Speeds Up Coding—Not the Other 80% of SDLC.

FASTER WITH AI (BOTH)
80% BEYOND CODING · NOT FASTER WITH AI (DOUBLED ON 2 NATIVE APPS)
20% Coding
25% Auto Tests
25% QA & Parity
30% Ownership
PHASE 1
~20%
Coding
Native + AI & Flutter + AI
PHASE 2
~25%
Automated Tests
2× Test Suites on Native
PHASE 3
~25%
Release QA & Parity
2× Logic & UI Verification
PHASE 4
~30%
Long-Term Ownership
2× Repos, PRs & Maintenance
  • • AI only accelerates 20% coding phase
  • • Flutter gets faster coding with AI
  • • 80% SDLC effort still doubles natively
11 / 23
SHOPIFY’S REBUILD TAX · 4 CUSTOM TOOLS FOR 30 ENGINEERS

AI Native Migrations Require Heavy Verification Harnesses.

01 · No One-Shot
02 · Match Running App
03 · Adversarial Audit
04 · Mandatory Gate
Helix
Checkpoints
→
Visual UI
Review
→
2 AI Critics
Review
→
“A Human’s
Nod”
  • • Weeks spent upfront on manual screens
  • • Built Helix, Reflex & cloud fleets
  • • Human approval gates every migration step
13 / 23
A BETTER HARNESS BEATS A BETTER PROMPT

Reflex Skips the UI; Flutter Tests Widgets Too.

Shopify Reflex (2 Codebases) Headless State Only (0% UI)
Flutter Test + MCP (1 Codebase) 100% Logic + Widgets (ms)
  • • Reflex skips SwiftUI and Compose UI
  • • Flutter tests logic and widgets in ms
16 / 23
WHERE CROSS-PLATFORM BEAT NATIVE

Shared Engines Win When Visuals Define Products.

70%+
Unity Cross-Platform Engine (70%+ Top 1,000 Mobile Games)
Native / Others
  • • Unity powers 70%+ of top games
  • • Studios avoid maintaining two 3D engines
  • • One shared engine beats building twice
17 / 23
VISUALIZATION AS THE PRODUCT

Brand Experiences Demand One Shared GPU Canvas.

  • • RealityKit and Filament feel visibly different
  • • Shaders and physics must match exactly
  • • Shared C++ engines recreate cross-platform tradeoffs
{ GLSL + 3D }
iOS vs Android visual parity
Swift/RealityKit ≠ Kotlin/Filament
19 / 23
Is Flutter the right choice for everything?
No. Here is where Native wins.
21 / 23
WHERE NATIVE WINS · 02 · TWO ORTHOGONAL AXES

Flutter Scales Horizontally; Native Owns OS Surfaces.

FLUTTER · HORIZONTAL CROSS-OS ↔
6 Operating Systems
iOS Android Web macOS Windows Linux
Shared App UI, Business Logic & 3D Canvas
NATIVE · VERTICAL OS SURFACES ↕
Deep System Surfaces
Apple Watch · Wear OS Tiles VisionOS · Android XR
WidgetKit · Glance · Live Activities
CarPlay · Android Auto · App Intents · tvOS
Requires SwiftUI / WidgetKit & Jetpack Glance
  • • Flutter spans mobile, web, and desktop
  • • Native owns Watch, TV, and spatial
  • • System widgets require SwiftUI or Glance
23 / 23
Thank You · Open-Source Demos & Agent Skills

Build Once with AI and Deterministic Flutter.

  • • Explore 3D demos in flutter_3d repo
  • • Try native embedding in flutter-inapp-ios
  • • Reuse agent skills for Stac workflows
Amorn Apichattanakul
Senior Innovation Engineer @KBTG
Repository QR Code
Scan for Slides, Demos & Skills