Flutter 3.47

Original Article ↗ Hacker News Discussion ↗

Flutter 3.47 prompts renewed debate over Google’s cross‑platform UI framework: many developers praise its productivity, performance, and ability to target mobile, desktop, web, and even embedded systems from a single Dart codebase, citing real‑world adoption by major companies. Others remain wary of Google’s long‑term commitment, Flutter’s weaker web story, and rough edges like rendering quirks or missing platform-native behaviors, and instead favor ecosystems around Kotlin, React Native, or fully native development augmented by AI. Overall, Flutter is seen as a mature, widely used option whose main risks are strategic rather than technical.

Project status and longevity

  • Many see Flutter as surprisingly resilient for a Google project, given Google’s history of shutting down popular tools.
  • Explanations offered: strong internal use (e.g., Google products, AdWords rewrite in Dart), cost savings from single mobile codebase, and inertia.
  • Some believe even if Google pulled back, ecosystem momentum and potential transfer to a foundation could keep it alive.
  • Others still avoid it due to fear of eventual “rug pull.”

Adoption and real-world usage

  • One camp claims “nobody uses it.”
  • Others counter with:
    • Big consumer apps (banks, Chinese tech companies, car makers, etc.).
    • Internal Google dogfooding.
    • Third‑party stats shared in the thread: ~16% of iOS apps and ~24% of Android apps using Flutter SDKs.
  • Several developers report successful production apps with large user bases.

Strengths highlighted

  • Single codebase for Android, iOS, desktop, and web with relatively consistent UI.
  • Strong dev experience: hot reload, fast iteration, good tooling, and straightforward Firebase integration.
  • Dart praised as simple, statically typed, null‑safe, with good FFI and AOT/JIT toolchain.
  • Good fit for “business CRUD” and cross‑platform apps where perfect platform nativeness is less important.

Criticisms and pain points

  • Concerns about Google’s commitment and lack of visibility in Android’s official docs.
  • Web support described as “basically unusable” for traditional websites; large downloads, canvas‑based rendering hurts tooling and accessibility.
  • Desktop performance and scrolling behavior (especially on iOS and web) called out as weak or inconsistent by some.
  • Devs note long compile times in some workflows, Impeller engine’s bumpy rollout, and slow arrival of features like multi‑window and HDR/wide‑gamut.
  • Some strongly dislike Dart’s syntax and semantics; others find Flutter code verbose and “ancient” compared to newer UI frameworks.

Flutter vs. alternatives

  • React Native: preferred by some for TypeScript/hiring, closer mapping to native UI, ecosystem breadth; others report worse performance, dependency hell, and poor app architectures.
  • Kotlin Multiplatform/Compose: seen as promising but still immature and more complex; tooling and Gradle ecosystem criticized.
  • Native + AI: multiple comments suggest AI‑assisted native development is eroding the traditional advantage of cross‑platform frameworks.