DroidKit Nothing is uploaded

Why your Android icon looks wrong on someone else's phone

17 November 2026

Android does not draw your icon. It draws a mask over two layers you supply, and the mask shape belongs to the launcher, not to you. Design for the 72dp circle in the middle of a 108dp canvas and the shape stops mattering.

The 108dp canvas and the 72dp you can trust

An adaptive icon has a foreground layer and a background layer, each 108dp square. The launcher masks both to whatever shape it uses — circle, squircle, rounded square, teardrop — and the device manufacturer decides which.

Only the centre 72dp is guaranteed to survive every mask. The 18dp border on each side is there so the system can move the layers for parallax and pulse animations. Anything you put in that border is decoration that some users will never see, and any artwork that crosses it gets clipped on the devices with the most aggressive mask.

This is the single most common icon mistake I see: a logo scaled to fill the 108dp square, which looks correct in Android Studio's preview and loses its edges on a Pixel.

Why the background layer should be boring

The background layer gets masked hardest and moves during animations. A flat colour or a simple gradient is the right answer almost every time. Detail there is wasted work, because the user sees a different crop of it on every launcher.

Put the recognisable part of your brand on the foreground layer, inside the safe zone, and let the background be the colour people remember.

Themed icons, and why yours is probably missing

Android 13 added monochrome icons. When a user turns on themed icons, the launcher takes your <monochrome> drawable and recolours it to match their wallpaper. Apps that did not ship one get left in full colour, sitting in a grid of tinted icons and looking like they were abandoned.

The drawable is declared alongside the other two layers:

<adaptive-icon>
  <background android:drawable="@color/ic_launcher_background" />
  <foreground android:drawable="@drawable/ic_launcher_foreground" />
  <monochrome android:drawable="@drawable/ic_launcher_monochrome" />
</adaptive-icon>

The monochrome layer must work as a silhouette. Shape carries it; colour is thrown away. If your logo is two tones of the same hue, the themed version collapses into a blob and you need a simplified drawing rather than a desaturated copy of the original.

The densities you still have to ship

Adaptive icons did not remove legacy icons. Devices below Android 8, and a few surfaces that ask for a plain bitmap, use the old 48dp square at five densities.

BucketScaleLegacy iconAdaptive layer
mdpi1.0×48 px108 px
hdpi1.5×72 px162 px
xhdpi2.0×96 px216 px
xxhdpi3.0×144 px324 px
xxxhdpi4.0×192 px432 px

Start from artwork at least 432 px square, or vector, and scale down. Scaling up from a 192 px export gives you a soft xxxhdpi icon that looks slightly out of focus next to every other app on a modern phone.

The Play Store icon is a separate file

512 × 512 PNG, 32-bit, and Play applies its own rounding. Two things get listings rejected here more than anything else: transparency, and an icon that already has rounded corners baked in, which then gets rounded again and ends up with a visible notch at each corner.

Send Play a full square with no alpha channel and let it do the rounding.

What to check before shipping

The App Icon Generator takes one image and writes every density, the adaptive layers, the monochrome drawable and the 512 px Play icon into a correctly structured res/ folder, with the 72dp safe zone drawn on the preview so you can see what a launcher would clip. For checking individual measurements, the dp ↔ px converter covers every bucket.