- From: Matt Giuca <notifications@github.com>
- Date: Thu, 18 Jul 2019 20:56:41 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 19 July 2019 03:57:03 UTC
Just to clarify this position: using maskable icons _will_ (at least in Chrome) create an adaptive icon in Android, it just won't have the 2 layers. So it will be used everywhere in Android that adaptive icons are needed, and also work properly on other operating systems once they implement it. We had a long discussion about the 2 layers thing and found that it was almost completely imperceptible even on Android. It's only noticeable when you are dragging an icon around on the home screen rapidly (the two layers parallax as you're dragging), but your finger is covering the icon so you have to look very carefully under your finger. Given this, we didn't see a reason to design and implement an Android-specific web API for something that almost nobody will ever notice. However, there is significant cross-platform value in having a large icon that can be cut out into whatever shape the operating system wants, thus we settled on maskable icons for the web spec. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/555#issuecomment-513080945
Received on Friday, 19 July 2019 03:57:03 UTC