Skip to content

Platform specific assets #8230

Open
Open

Description

@lukef

It would be great if you could use a platform (android/iOS) as a variant (automatically) with regards to Assets.

A good example is for icons representing actions like sharing. They have platform specific conventions and it would be great if you could just do "assets/icons/share" and have the one that is relevant to the current platform.

Activity

  1. eseidelGoogle commented on Feb 17, 2017

    @eseidelGoogle
    Contributor

    #7111 is also related to the specific share case.

  2. added this to the milestone on Feb 28, 2017
  3. Hixie commented on Feb 28, 2017

    @Hixie
    Contributor

    How important is this for you? We have a way to add support for this, so if it's something you definitely need and don't want to work around we can add it, otherwise it's something we would not add in the near future.

  4. lukef commented on Mar 1, 2017

    @lukef
    ContributorAuthor

    We built out a mechanism (happy to share) that meets our requirements for now so we are not in a huge rush. Could mark as lower priority.

  5. added
    toolAffects the "flutter" command-line tool. See also t: labels.
    a: assetsPackaging, accessing, or using assets
    on Nov 28, 2018
  6. sestegra commented on Dec 18, 2018

    @sestegra

    See my proposal #25487

  7. removed this from the milestone on Jun 1, 2020
  8. fzyzcjy commented on Sep 1, 2020

    @fzyzcjy
    Contributor

    We built out a mechanism (happy to share) that meets our requirements for now so we are not in a huge rush. Could mark as lower priority.

    @lukef Hi could you please kindly share your mechanism? I am having a possibly related (though different) question here. Thanks!

  9. xuzhongpeng commented on Dec 5, 2022

    @xuzhongpeng

    What is the current progress?

  10. rajrushilmakkar commented on Feb 9, 2023

    @rajrushilmakkar

    We built out a mechanism (happy to share) that meets our requirements for now so we are not in a huge rush. Could mark as lower priority.

    @lukef Hi could you please kindly share your mechanism? I am having a possibly related (though different) question here. Thanks!

    Can any of you guys please share the mechanism that you used? I have a similar use case where I want to include the assets only on iOS and not on web/android
    Thanks!

  11. added
    P3Issues that are less important to the Flutter project
    and removed on Jun 28, 2023
  12. littleGnAl commented on Aug 3, 2023

    @littleGnAl
  13. hwkim1127 commented on Jul 12, 2024

    @hwkim1127
  14. added
    tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.
    on Jun 30, 2025
  15. alnitak commented on Nov 13, 2025

    @alnitak

    I think this issue can be closed since #176393 has been merged.

  16. AbdeMohlbi commented on Dec 1, 2025

    @AbdeMohlbi
    Member

    @tirth-patel-nc can we close this , it seems the mentioned feature have been implemented and merged to the framework

  17. tirth-patel-nc commented on Dec 3, 2025

    @tirth-patel-nc
    Member

    in #176393, linked issue is #65065.


    From #8230:

    (Why not duplicate of #8230 : I want to bundle those 1MB photos only in Android. Thus, in the final .ipa file of iOS, there are no such photos taking space.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projecta: assetsPackaging, accessing, or using assetsc: new featureNothing broken; request for a new capabilitycustomer: posse (eap)team-toolOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.triaged-toolTriaged by Flutter Tool team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions