You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 25, 2024. It is now read-only.
Our designers also maintain app icons and the store images in figma. Therefore I am wondering, whether the app icon generation can also be automated by parabeac. This would be beneficial, since then figma is the single source of truth relating to design and the changes of the figma file could automatically be reflected within the project.
Hi @ivan-015,
cool!
I have spoken to our design team and they say, we should use something like:
app_icon_[android|ios]_<pixels_width>.
IMO some kind of logic should be applied that if I have any icons supplied that can directly be copied to the app, they should be used instead of letting the launcher icons package do its work. Only the ones that are missing should be supplied by the launcher icons package. Therfore maybe it should be mandatory to provide a 1024x1024 px icon named app_icon_default that is taken into account, when it is not possible to directly copy any other icon.
Thanks for considering to implement this :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Our designers also maintain app icons and the store images in figma. Therefore I am wondering, whether the app icon generation can also be automated by parabeac. This would be beneficial, since then figma is the single source of truth relating to design and the changes of the figma file could automatically be reflected within the project.
Idea: This feature could be implemented by facilitating the flutter launcher icons package.
The text was updated successfully, but these errors were encountered: