Re: [w3c/manifest] Themed/colored icons for web apps (Issue #1091)

@NotWoods is correct. This is precisely what `monochrome` icons were designed for.

Note that I don't think these have been implemented by any user agent for main app icons (they are used, e.g. on Android for shortcut icons). That means there's an opportunity for browsers to implement this spec for main app icons when exposed to an environment like Android Themed Icons. It also means sites need to start adding `monochrome` icons, which we can't expect them to do when no browser supports it. But there's no deficiency in the spec as far as I can see.

I take your point @filips123 that there is no way to specify a combination of "maskable" and "monochrome" at the same time. However, I don't think that's required here. The reason why `maskable` has a safe zone is because in that context, the OS is cutting a circle shape around a "full bleed" image. The application needs to specify a much larger image than the circle, extending a solid colour or pattern outwards, so that the OS can cut any shape it wishes out of that background.

In the case of `monochrome`, there is no need for the application to specify any extraneous pixels, since the background is, by definition, transparent. `monochrome` is much closer to a traditional icon: you have an image size (say 256x256), the icon fills up the entire space, maybe with a small amount of padding, and then the OS embeds that image inside a shape like a circle, leaving as much margin as it wishes. The only difference to a traditional icon is that there is no colour defined in the icon itself (the colour is selected by the OS). I believe that `monochrome` by itself is perfectly suitable for use as an Android Themed Icon.

Based on the above explanation, I'm going to close this (already implemented). Feel free to reopen or continue discussing if you think there is some aspect of Android Themed Icons that is not covered by `monochrome` as defined by the Manifest spec.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1091#issuecomment-1566327546
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1091/1566327546@github.com>