All "adaptive icons" means is that every unique icon has to be constrained in a circle. It makes every icon look monotonous and, in some cases, shrinks the icon so that they're hard to see even on large screens.

There's a cognitive element here. When I look at my screen for an icon, I tend to use colour and shape to find what I'm looking for. With every icon now a circle, and half of them trapped in a white background, it makes looking for the right icon harder.

Boring!

Better!

Æsthetics

This is the way I personally prefer my icons. I don't care that they're not a uniform shape. I don't care that some of them have a lower centre of gravity than others. I don't care that the corner radius is different on each one. I don't care that they don't all line up perfectly like ticky-tacky little boxes.

I want them not to be the same.

Getting the icons

Here's how to fix it.

This is the Gmail adaptive icon - tiny and indistinct.

The Gmail app lives at: https://play.google.com/store/apps/details?id=com.google.android.gm

Inspecting the source code shows the nice large icon lives at: https://lh3.ggpht.com/8-N_qLXgV-eNDQINqTR-Pzu5Y8DuH0Xjz53zoWq_IcBNpcxDL_gK4uS_MvXH00yN6nd4=s180

Removing the =s180 from the end of the URl gives us the full 512x512 image. That's suitable for use as an alternative icon.

OK, but how do we get the icon from the Play Store URl? Google intentionally make this difficult. You'd think that it would be <div id="icon"><img id="icon-small" ...> or something. Nope!

Here's what the source looks like:

What the flippity-flack is going on there? Purposefully uglified code designed to obfuscate and frustrate?

At the moment, it looks like all icon images have class="T75of ujDFqe" - but I wouldn't want to bet on that being stable.

There's no official API for Google Play - but there are unofficial paid-for APIs and some open source scrapers of varying usefulness.

I ended up using Daniel Liu's Python Play Store Scraper.

This quick scrap of code take's an app's package name, downloads the large size icon, compresses it using WebP, and saves it.

import play_scraper
import requests
from PIL import Image
import webp

packageName = "com.android.chrome"
icon = Image.open(requests.get(play_scraper.details(packageName)["icon"], stream = True).raw)

# Save as png
icon.save(packageName + ".png", optimize=True)

#Save as WebP
webp.save_image(icon, packageName + '.webp', lossless=True)

Setting the icon

Most modern Android homescreens allow you to manually set the icons of each app. Long press on an app, then choose edit, then select the icon you want. Easy! (ish)

If I Was Clever

If I had the skill, I'd create an Android app which looked at the app name, downloaded the icon from the play store, and used that as the launcher icon.

Or, I'd fork an existing icon pack and manually add the top 500 apps.

But I'm not that good at Android apps. If anyone else wants to make it, please do so!

I found a curious case where some WebP images are rendered upside down!

On the left is Opera for Android, centre is Chrome for Android, and on the right is Firefox for Android. Firefox is the only one which renders the lower image correctly. The upper image is also WebP.

This also seems to affect iOS.

Terence Eden is on Mastodon

@edent

Replying to @paulglavin@paulglavin so I'm not seeing things? That's good to know. Any chance of a screenshot?

---

Paul Glavin

@paulglavin

Replying to @edent@edent I can't guarantee you're not seeing things! pic.x.com/o48z3ywmlq

---

The original article has since replaced the WebP images with standard JPGs - but I managed to grab one of the images before they were removed.

(Photo via David Wilfert)

I'm not sure if my Android phone has somehow mangled the file when it was saved, or whether the image was like that to start with.

There are, I suppose, three possibilities.

1. Both iOS and Android have a bug with rendering some WebP images.
2. Buzzfeed's CDN has a bug which rotates some WebPs - and doesn't serve them to Firefox due to lack of support.
3. A collective hallucination.

For now, I'm tempted to put the blame on a buggy image conversion - that seems to be the simplest explanation. Either way, a salutary reminder to check your content in several different browsers.