Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Flutter 3.50 is out: Material and Cupertino are deprecated - here's the migration path

Flutter 3.50 shipped on 11 November with Dart 3.14. The headline change is not a widget or a performance graph - it is a structural one: the Material and Cupertino libraries bundled with the framework are now formally deprecated, and their future lives in standalone packages. The Material/Cupertino split Flutter's bundled material and cupertino libraries are deprecated in 3.50. The replacements…

Flutter 3.50, released on November 11th, brings a significant structural change to the framework: the Material and Cupertino libraries are now formally deprecated. These libraries, previously bundled within the framework, will now exist in standalone packages named material_ui and cupertino_ui, versioned independently of Flutter.

The move aims to simplify design library updates, allowing them to be shipped without waiting for a framework release, and give the framework team more flexibility in evolving without carrying deprecated libraries.

To facilitate the transition, a MaterialUiCompatibilityBridge is available for code that straddles both worlds during the migration. Dart fix, a tool, applies the majority of the changes required for the migration, making the process largely mechanical. The official migration guide, found on docs.flutter.dev, provides comprehensive instructions for the transition.

In addition to the Material/Cupertino deprecation, Flutter 3.50 introduces several enhancements. Native interop, or the ability to call native code on various platforms, has been consolidated in a new section of the documentation. This includes guides for Pigeon, package:ffigen (for C and Objective-C), package:jnigen (for Java and Kotlin), and build hooks for bundling native code.

Web development in Flutter continues to improve with new features. A --web-content-hash build flag has been added to add cache-busting hashes to web assets, improving cache control. The WebAssembly (Wasm) documentation now covers critical production concerns such as server headers, pre-compression, cold-start latency, CDN asset loading, and profiling Core Web Vitals in Chrome DevTools.

Finally, the platform-integration docs have been updated to cover iOS 27, macOS 27, and Xcode 27. Expanded Swift Package Manager migration guidance for apps and plugins is now available, ensuring Apple platform readiness.

Before upgrading to Flutter 3.50, it is recommended to run your test suite, review the breaking changes listed, and assess your plugin stack. While the Material/Cupertino deprecation does not remove these libraries from your app, starting the migration early with the provided tools and documentation is less costly than attempting it during a time-sensitive deadline later.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

Synology CVE-2026-120382: How to Check Your NAS (DSM 7.2 Has No Patch Yet)

If your Synology NAS runs DSM 7.2 and can be reached from the internet, CVE-2026-120382 is a CVSS 9.8 bug that needs no password and no click.

  • Synology NAS devices with DSM 7.2 vulnerable to CVE-2026-120382.
  • No patch available for DSM 7.2 as of November 2026.
  • Upgrade to DSM 7.3.2-86009-6 or higher to mitigate risk.

Journald logs: ship them to Dynatrace with OneAgent

You open a recent Linux node to look for an error and there is no file to read: everything goes through systemd. The journald logs stay on the machine in a binary format, and they vanish with it if…

  • Journald logs collected via OneAgent log module
  • OneAgent reads journal through systemd API
  • Enable Journald log detector and "Ingest Journald logs" rule

How Many Websites Use Next.js? 1.97M Sites, and How to Spot One With curl

As of November 16, 2026, webatla counts 1,973,502 websites running Next.js, 0.61% of the 325.8 million websites it tracks.

  • As of November 16, 2026, Next.js powers 1,973,502 websites.
  • Detect a Next.js site by checking for specific markers in HTML or response headers.
  • Use curl command to verify Next.js presence in response headers.

More from Saturday 21 November →