[UWP] Which asset is used for the default toast notification icon in 1607?

Question

Hello, I have some questions about which asset is used for the default toast notification icon in Windows 10 1607.

1. What is the filename of the package.appxmanifest asset that it prefers? (for example, Square44x44Logo.targetsize-16 or the altform_unplated version)
2. Is a different asset chosen for each screen DPI scaling percent or is it fixed?
3. If the proper assets are provided, will that prevent the system from resizing it or is it now a non-standard size?

I'm seeing a very blurred/scaled icon there, so I'd like to get it fixed. Thanks for your time.

Answer 1

Hi Nobody31,

>>What is the filename of the package.appxmanifest asset that it prefers? (for example, Square44x44Logo.targetsize-16 or the altform_unplated version)

We can set the image to the Square44x44Logo.

>>Is a different asset chosen for each screen DPI scaling percent or is it fixed?

Yes, when we does not provide other size asset it will fixed.

>>If the proper assets are provided, will that prevent the system from resizing it or is it now a non-standard size?

No, the system will resizing it if there is no other proper size of the assets.

Best Regards,

Jayden Gu

Answer 2

On my PC at 100% DPI scaling (default), it seems to be using "Square44x44Logo.targetsize-48_altform-unplated.png" for the toast notification icon and resizing it from 48x48 to 16x16, even though I'm also providing 16x16 with both a "Square44x44Logo.targetsize-16.png" and a "Square44x44Logo.targetsize-16_altform-unplated.png". The "Square44x44Logo.targetsize-48_altform-unplated.png" asset is also being used as the taskbar app icon when set to show small icons.

I'm guessing it would be a bad idea to provide a 16x16 image for the targetsize-48. How can I avoid this resizing?

Answer 3

Hey, this is Andrew from the Windows Notifications team!

Action Center currently uses the targetsize-32 image. And therefore, if that isn't included, it will use the next larger size, which in your case is 48x48.

So if you provide the 32 target size, you should be able to get slightly better results.

Note that it currently always uses the 32x32 image, regardless of your DPI scaling options. 32 was picked so that it would look reasonable at both 100% and 200% (and somewhat reasonable at 400%).

Thanks!
Andrew

Answer 4

That makes a lot more sense, as I only have targetsize-16, 24, 48, and 256, which are provided slots on the package.appxmanifest editor in Visual Studio. I'll see how it looks with 32. Will size 32 get a slot on the appxmanifest Visual Assets editor soon? I'll mark that as the answer for now. Thanks for your reply!