<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/nSjLzKy7x" -->

---
title: Material and Cupertino decoupling are here | daily.dev
description: Flutter has decoupled its Material and Cupertino UI libraries from the core framework, releasing them as standalone pub.dev packages (pkg:material_ui and...
canonical: https://daily.dev/posts/material-and-cupertino-decoupling-are-here-nsjlzky7x
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Material and Cupertino decoupling are here | daily.dev
og:description: Flutter has decoupled its Material and Cupertino UI libraries from the core framework, releasing them as standalone pub.dev packages (pkg:material_ui and...
og:url: https://daily.dev/posts/material-and-cupertino-decoupling-are-here-nsjlzky7x
og:image: https://api.daily.dev/og/posts/nSjLzKy7x.png
og:image:alt: Material and Cupertino decoupling are here
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Material and Cupertino decoupling are here

**[Flutter](https://daily.dev/sources/flutter)** · 5 min read · 38 upvotes · 4 comments

## Summary

Flutter has decoupled its Material and Cupertino UI libraries from the core framework, releasing them as standalone pub.dev packages (pkg:material_ui and pkg:cupertino_ui) at version 1.0.0 as of August 13, 2026. The move aims to reduce upgrade friction, since Flutter upgrades previously bundled UI changes with framework updates, and to let these design libraries ship on faster, independent release schedules instead of waiting for Flutter's quarterly stable releases. The Flutter team says it remains fully committed to maintaining both libraries and recommends using dart fix to migrate imports, describing it as a drop-in change. The core widgets library will also be strengthened to better support third-party design systems like macos_ui, fluent_ui, and shadcn.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://flutter.dev/blog/decoupling-material-cupertino>

## Questions this post answers

### How do I migrate my Flutter app from flutter/material.dart to the new material_ui package?

Run dart fix in your Flutter project to automatically add the standalone material_ui and cupertino_ui packages to pubspec.yaml at version 1.0.0 and replace the old imports. This is expected to be a drop-in migration since version 1.0.0 is an exact replica of the in-framework state as of the split. File a GitHub issue on the flutter/flutter repo if problems occur.

_Track migration guidance for Flutter's material_ui and cupertino_ui split on daily.dev before rolling out the upgrade._

### Why did Flutter move Material and Cupertino out of the core framework into separate packages?

Bundling Material and Cupertino UI updates with every Flutter framework release meant security patches and other fixes always dragged UI changes along, creating major upgrade friction that kept teams on older versions and could cost weeks of developer effort per upgrade. Splitting them into pkg:material_ui and pkg:cupertino_ui, released on pub.dev at version 1.0.0 in August 2026, lets Flutter upgrades stay simple while Material and Cupertino ship on independent weekly schedules instead of waiting up to 16 weeks for Flutter's quarterly stable release.

_Developers weighing Flutter upgrade timing can follow how the material_ui and cupertino_ui split changes that process on daily.dev._

### Are the Flutter Material and Cupertino libraries still maintained by Google after being moved to pub.dev?

Yes, the Flutter team continues to give material_ui and cupertino_ui the same level of attention as before, and as of August 13, 2026 they are also open for contributions from any Flutter developer. The move is not a deprioritization; it is meant to accelerate development pace, including ongoing work on Liquid Glass and Material 3 Expressive implementations.

_Flutter developers deciding whether to trust these packages long-term can follow their maintenance status on daily.dev._

## Community discussion

Top comments from developers on daily.dev.

**@romeltech** · 1 upvotes

> Is it time to upgrade?

**@agustinbarrientos** · 0 upvotes

> I think this split is overdue. A small Material fix shouldn't drag the whole Flutter SDK along for the ride.

**@barneysspeedshop** · 0 upvotes

> It's about damn time

## Similar posts on daily.dev

- [How Flutter’s Material and Cupertino Decoupling is Changing Cross-Platform UI Development](https://daily.dev/posts/how-flutter-s-material-and-cupertino-decoupling-is-changing-cross-platform-ui-development-q9slpuvxn) · Flutter Community · 0 upvotes · 0 comments
- [Decoupling Material and Cupertino in Flutter: Why It Matters and How to Adapt](https://daily.dev/posts/decoupling-material-and-cupertino-in-flutter-why-it-matters-and-how-to-adapt-t07wzsmoc) · freeCodeCamp · 3 upvotes · 0 comments
- [Flutter’s Material and Cupertino code freeze](https://daily.dev/posts/flutter-s-material-and-cupertino-code-freeze-ptpowftya) · Flutter · 13 upvotes · 0 comments
- [Moving a Flutter App to material\_ui and cupertino\_ui: The Import Swap Is the Easy Part](https://daily.dev/posts/moving-a-flutter-app-to-material-ui-and-cupertino-ui-the-import-swap-is-the-easy-part-7wgdoqph4) · Medium · 0 upvotes · 0 comments

---

Tags: [#mobile](https://daily.dev/tags/mobile), [#flutter](https://daily.dev/tags/flutter), [#dart](https://daily.dev/tags/dart)

[View this post on daily.dev](https://daily.dev/posts/material-and-cupertino-decoupling-are-here-nsjlzky7x)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Material and Cupertino decoupling are here","url":"https://daily.dev/posts/material-and-cupertino-decoupling-are-here-nsjlzky7x","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/material-and-cupertino-decoupling-are-here-nsjlzky7x"},"datePublished":"2026-09-10T00:54:27.790Z","dateModified":"2026-09-14T08:48:34.406Z","description":"Flutter has decoupled its Material and Cupertino UI libraries from the core framework, releasing them as standalone pub.dev packages (pkg:material_ui and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8689f30d45a0af17dace9ffad70797a8?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8689f30d45a0af17dace9ffad70797a8?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Flutter","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Flutter","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/flutter","url":"https://daily.dev/sources/flutter"},"commentCount":4,"discussionUrl":"https://daily.dev/posts/material-and-cupertino-decoupling-are-here-nsjlzky7x","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":38},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":4}],"keywords":"mobile,flutter,dart","timeRequired":"PT5M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Flutter","item":"https://daily.dev/sources/flutter"},{"@type":"ListItem","position":3,"name":"Material and Cupertino decoupling are here"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/material-and-cupertino-decoupling-are-here-nsjlzky7x","comment":[{"@type":"Comment","text":"Is it time to upgrade?","datePublished":"2026-09-10T04:56:09.997Z","url":"https://daily.dev/posts/nSjLzKy7x#c-Dt7ebnU2N","author":{"@type":"Person","name":"Romel","url":"https://daily.dev/romeltech","image":"https://lh3.googleusercontent.com/a/ACg8ocLXdVM7dm8jXeGczNpFrzBpySAvTP-5-3hA50WtCchAWgPZBvRQ=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}},{"@type":"Comment","text":"I think this split is overdue. A small Material fix shouldn’t drag the whole Flutter SDK along for the ride.","datePublished":"2026-09-12T21:59:34.607Z","url":"https://daily.dev/posts/nSjLzKy7x#c-9a7sLqBlm","author":{"@type":"Person","name":"Agustin Barrientos","url":"https://daily.dev/agustinbarrientos","image":"https://media.daily.dev/image/upload/s--5ayxQnqn--/f_auto/v1788281802/avatars/avatar_wQYYVe5Tbj0NJ7C7qPoa8?_a=BAMAMicg0"}},{"@type":"Comment","text":"It’s about damn time","datePublished":"2026-09-18T03:02:25.453Z","url":"https://daily.dev/posts/nSjLzKy7x#c-3f14k87kL","author":{"@type":"Person","name":"Barney's Speed Shop","url":"https://daily.dev/barneysspeedshop","image":"https://lh3.googleusercontent.com/a/ACg8ocKUOwM8vHpJpu-6xy8V-8casTQY5b-cloJ5dT82k3IVRm-z2BYY2Q=s96-c"}}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/material-and-cupertino-decoupling-are-here-nsjlzky7x#faq","mainEntity":[{"@type":"Question","name":"How do I migrate my Flutter app from flutter/material.dart to the new material_ui package?","acceptedAnswer":{"@type":"Answer","text":"Run dart fix in your Flutter project to automatically add the standalone material_ui and cupertino_ui packages to pubspec.yaml at version 1.0.0 and replace the old imports. This is expected to be a drop-in migration since version 1.0.0 is an exact replica of the in-framework state as of the split. File a GitHub issue on the flutter/flutter repo if problems occur. Track migration guidance for Flutter's material_ui and cupertino_ui split on daily.dev before rolling out the upgrade."}},{"@type":"Question","name":"Why did Flutter move Material and Cupertino out of the core framework into separate packages?","acceptedAnswer":{"@type":"Answer","text":"Bundling Material and Cupertino UI updates with every Flutter framework release meant security patches and other fixes always dragged UI changes along, creating major upgrade friction that kept teams on older versions and could cost weeks of developer effort per upgrade. Splitting them into pkg:material_ui and pkg:cupertino_ui, released on pub.dev at version 1.0.0 in August 2026, lets Flutter upgrades stay simple while Material and Cupertino ship on independent weekly schedules instead of waiting up to 16 weeks for Flutter's quarterly stable release. Developers weighing Flutter upgrade timing can follow how the material_ui and cupertino_ui split changes that process on daily.dev."}},{"@type":"Question","name":"Are the Flutter Material and Cupertino libraries still maintained by Google after being moved to pub.dev?","acceptedAnswer":{"@type":"Answer","text":"Yes, the Flutter team continues to give material_ui and cupertino_ui the same level of attention as before, and as of August 13, 2026 they are also open for contributions from any Flutter developer. The move is not a deprioritization; it is meant to accelerate development pace, including ongoing work on Liquid Glass and Material 3 Expressive implementations. Flutter developers deciding whether to trust these packages long-term can follow their maintenance status on daily.dev."}}]}
```

