Repository navigation
[packages] Migrate packages to material_ui and cupertino_ui #191322
Description
Several packages depend on Material or Cupertino:
- go_router
- animations
- video_player
- google_maps_flutter
- image_picker
- camera
- webview_flutter
- file_selector
- interactive_media_ads
And several more in their examples:
- path_provider
- google_fonts
- in_app_purchase
- local_auth
- pointer_interceptor
- extension_google_sign_in_as_googleapis_auth
- url_launcher
- shared_preferences
- google_adsense
- web_benchmarks
- vector_graphics
We should migrate these to material_ui and cupertino_ui. Or, perhaps we should even refactor them to remove the dependency where possible.
Activity
ricardodalarme commentedon Aug 27, 2026
I opened a PR to kickstart this migration: flutter/packages#12648. Can we assume it's fine to add
material_uiorcupertino_uito any example? Bc I suppose we want to have as fewmaterial_uiandcupertino_uidependencies as possible in the actual packages, but in the examples, can we agree that adding them is fine?justinmc commentedon Sep 25, 2026
Sorry I missed this, yes adding material_ui and cupertino_ui to other packages where they are using them today (especially in examples) should be fine.
[cupertino_icons] Migrate to `cupertino_ui` (#12649)
SangWook16074 commentedon Sep 29, 2026
I’m looking into the pointer_interceptor_ios example as a possible small contribution to this migration. I couldn’t find an existing PR for that example. Is it already being handled as part of another PR, or would a separate PR be useful?
[vector_graphics] Remove unnecessary Material imports (#12798)