Scenario value of Make Round Image in icon
`app-icon-mask-circle` supports 应用图标预览场景. Keep composition consistency, edge quality, and destination readability stable with pilot validation, staged rollout, and anomaly logging.
`app-icon-mask-circle`: design for 29px legibility first, inset per platform safe templates, ship full density ladders
- Draw a “minimum readable box” at 29–36px—if the motif collapses, return to vector and delete secondary filigree and thicken primary strokes. Center mass should dominate portrait-style photos; symmetric marks snap to pixel grids to avoid shimmer.
- Overlay official iOS and Android mask templates; shrink 4–8% if corners get clipped. If brand colors vanish on OLED black wallpapers, document a dark-wallpaper variant with a compliant outer ring—discoverability beats pretending everyone uses light home screens.
- Export the 1024 master plus mdpi/hdpi/xhdpi slices with consistent naming; add light noise to long gradients before PNG quantize to fight store compression banding. Keep marketing previews versioned separately from review binaries to avoid store drift.
Round app-icon FAQ: tiny-size mush, stroke floors, dark wallpaper contrast, dual masks, gradient banding
Critiques look sharp on a 5K monitor but the launcher shows a blob—crop fault or design fault?
Almost always information overload—redesign for the target px rather than sharpening. Capture actual launcher tiles as the review canvas; circular export cannot rescue hyper-detailed illustrations.
1px line icons turn dashed after rounding—how to keep brand “hairlines”?
Obey vendor minimum stroke widths or convert to filled simplified geometry. Aesthetic purity cannot trump OCR/accessibility reality—document expected degradation if leadership insists on ultra-thin rules.
Icon camouflages on black wallpaper—does a white rim violate brand?
Treat it as a regulated adaptation: micro rings or plates approved in the guideline exceptions. Users finding the app matters more than a Figma artboard on #FFFFFF.
One PNG for both stores yet Android eats more corner—why?
Mask curvature differs—generate per-platform masters from shared vectors instead of hoping one raster survives both pipelines.
Flat gradients show concentric bands after store transcode—bit depth or compression?
Often 8-bit ramps plus storefront recompression—ease gradients, add dither, avoid multiple lossy saves, and verify by downloading the live package, not only local exports.