Acknowledged
7 months ago

automatically resize the app icon instead of issueing the warning that the app icon will be resized

we all know the warning:

WARNING: vivoactive3: The launcher icon (40x40) isn't compatible with the specified launcher icon size of the device 'vivoactive3' (40x33). Image will be scaled to the target size.

is it really that bad that the icon will be resized? is it worthy of raising a warning and polluting the build output? 

to answer the question:

I don't think it's worth it.

In the new app I'm writing I went to the trouble to create resource overrides so that each device has the icon prebaked in it's preferred resolution. I had to create 47(!!!) resource override folders just to get rid of this warning.

What I'm doing manually (resizing the icon and saving it in it's specific resource folder) is nothing different than what the compiler does automatically if the icon is not in the desired icon size.

I think:

- this warning has no (/not much) benefit and should be removed.

 

peterdedecker
Parents
  • 7 months ago

    For example, here's the Garmin nap glance icon (40 x 40, taken from a FR955 screenshot):

    Here's what it looks like after resizing to 33 x 33 using nearest neighbour (no colour blending):

    Pretty bad, right? Sure, I can get better results with a better resizing algorithm that blends the colours of neigbouring pixels, but that would probably require more colours than a MIP device has (64).

    Nonetheless, I tried it:

    Looks great, right?

    I expanded the image canvas size to 40 x 40 (pixels were added without changing any of the existing pixels), and set the new pixels to black, then used this image as a launcher icon for a device app.

    I tried it out on my fr955 and took a screenshot:

    This looks noticeably bad to me (certainly worse than the original icon), both on the real device and on my computer monitor, especially when it comes to the Zs. I think this would be the case for any sharply defined elements (like letters or numbers).

    Also, if no one cares about automatic launcher icon resizing, why did Garmin add the ability to use SVG files? Perhaps for people who want their icons to be automatically resized *and* look good?

Comment
  • 7 months ago

    For example, here's the Garmin nap glance icon (40 x 40, taken from a FR955 screenshot):

    Here's what it looks like after resizing to 33 x 33 using nearest neighbour (no colour blending):

    Pretty bad, right? Sure, I can get better results with a better resizing algorithm that blends the colours of neigbouring pixels, but that would probably require more colours than a MIP device has (64).

    Nonetheless, I tried it:

    Looks great, right?

    I expanded the image canvas size to 40 x 40 (pixels were added without changing any of the existing pixels), and set the new pixels to black, then used this image as a launcher icon for a device app.

    I tried it out on my fr955 and took a screenshot:

    This looks noticeably bad to me (certainly worse than the original icon), both on the real device and on my computer monitor, especially when it comes to the Zs. I think this would be the case for any sharply defined elements (like letters or numbers).

    Also, if no one cares about automatic launcher icon resizing, why did Garmin add the ability to use SVG files? Perhaps for people who want their icons to be automatically resized *and* look good?

Children
No Data