-
-
Notifications
You must be signed in to change notification settings - Fork 4
FAQ
In this section, you can find answers to questions that are not related to Troubleshooting. You can read about the background and history of this project and everything related to it in question-and-answer form.
Oh, it's a long story. None of the solutions that existed at the moment met the needs of the author. The most popular solution in the year 2020, was to use a package whose settings need to be controlled from the command line and a YAML file. It's a Dart way, not a Flutter way, the right UX (when it comes to visual elements) is the need for visual contact with the result. Also, the other solutions created icons only for mobile platforms, but Flutter offers much more. They didn't offer file validation which resulted in a large number of misunderstandings and App Stores rejections. Users didn't even know the basic entry details of the icon file, such as size, resolution, file-size, color profile, etc. How can you check the adaptive icon look and parallax effect there? How to check the safe zone of the latest "Maskable" PWA icons? How to preview the look on a real device? And much more. All these disadvantages were the reason for creating this open source and free product.
P.S. None of this means that the other projects are poor. They are great, I use some of them for automotive development too. I have written several articles to propagate them, but they are created for different types of tasks, for a different way of development.
Why export to an archive? Why not specify the path to the project directory and replace the icons directly?
There are several reasons for this:
- Loss of portability.
- The project was created (among other reasons) for designers too. They could have checked all the files before replacing them. Yes, please, never use generated 16x16px icons from a 1024x1024px file. Refine them in any graphic editor.
- Sequential archives generation is supposed here. The moment where you export icon files for certain platforms and then combine all these archives into one and replace the default icons with it.
- It's unbelievable, but not everyone uses VCS, and replacing icons directly is unacceptable for them. I've seen such cases :(
- It's a better UX solution.