Framework · 2017–now · Platform Wars
Flutter
Paint your own pixels on iOS and Android from one codebase. Google's bet against native UI fragmentation.
Flutter stuck where teams want one UI team and accept non-native feel for speed. Dart was a hurdle; tooling maturity lowered it. It will not kill Swift or Kotlin but owns greenfield cross-platform niches.
Context
Frameworks fought for the runtime
Front-end frameworks consolidated power; TypeScript became table stakes; Next and friends absorbed routing, data, and deploy gravity. Serverless and Jamstack rebranded old ideas with better CDNs, then cooled when auth and personalization refused to stay static. Blockchain-for-CRUD and big-bang rewrites collected dumb budgets. The winners were boring platforms with ecosystems — React gravity, Rust where systems care, Vite for greenfield bundling. The losers were narratives that skipped product-market fit or treated every App Router rewrite as destiny.
Compare with
Related
Framework · 2015–now
React Native
React components on native views. Share logic with web until platform differences ruin your sprint.
Language · 2011–now
Kotlin
Java without the boilerplate ceremony. Google's Android pick and Spring's polite nod kept it climbing.
Language · 2014–now
Swift
Apple's successor to Objective-C. The price of admission to serious iOS and macOS development.