Google Play icon design specifications
Apps & Computer Games around Google Play are embracing a brand new system to fit diverse programmer art to the various UI designs, shape factors, and apparatus of Google Play, and to create attention and also an appearance. Contours are easier to consume and visually appealing. They help users concentrate on art, as opposed. They mend problems brought on by arbitrary space to present info, like price, evaluation, and the name.
|Freeform – original format||The uniformed – new format|
This section describes some guidelines you should follow when creating visual assets for your app on Google Play.
|Total asset size||Product icon key lines|
After the asset is uploaded, Google Play dynamically applies the rounded mask and shadow to ensure consistency across all app/game icons.
On the left-hand side is your new icon asset. The following three images on the right-hand side show Google Play dynamic processing of the icon.
Utilize the full asset space as the background when dealing with minimalistic artwork.
Use the keylines as guides for positioning artwork elements (i.e. logos).
|Your full bleed artwork (final asset)||The end result with shadows and rounded corners dynamically applied by Google Play|
Don’t force your logo or artwork to fit the full asset space. Instead, utilize the keyline grid.
Don’t force drastic brand & artwork transformation to full bleed
Place freeform icon artwork on keylines instead
Illustrated artwork typically works well as a full bleed icon.
Don’t scale down illustrated artwork onto keylines
Google Play will dynamically add a drop shadow around the final icon once uploaded.
When adding shadows inside your icon artwork, consider consistency with the Android platform by following Google Material guidelines.
Don’t add drop shadows to your final asset
You can create shadows and light within the artwork
Google Play dynamically applies the corner radius. This ensures consistency when the icon is resized across different UI layouts. Radius will be equivalent to 20% of icon size.
Don’t round the edges of your final asset
Fill your entire asset with the artwork when possible
Embedded badges take away from the artwork itself and don’t scale down well with the icon.
Avoid communicating promotions on your artwork
Avoid using branding badges
If shapes are a critical part of a logo, do not force the artwork to full bleed. Instead, place it on the new keyline grid.
If possible, pick a background color for your asset that’s appropriate for your brand and doesn’t include any transparency. Transparent assets will display the background color of the Google Play UI.
If there is no distinct shape around a logo defining it, place it on a full bleed background.
If your artwork is flexible enough, consider tweaking it to fully utilize the asset size. If that’s not possible, revert to placing the logo on a keyline grid.
Uploading a icon each the specification won’t be allowed at the time of May 20-19. Watch details. Initial icon resources which have yet to be upgraded each the specifications will gradually be migrated to heritage style and scaled-down 75 percent into the key line grid size (512 * 0.75 = 384px).
Instructions for API users
To utilize the specification. All calls for Edits.images: that the upload will likely employ whatever specification is configured from the Play Console. There’s no method to employ the specification via API. The Edits.images: Hide telephone might possibly mistake if the older specification remains employed, and also the error message for this particular icon will direct you for the specification. Until it is going to triumph, you might want to retry the telephone times.
Achieve the same result of migrating all other f icons to the brand newest specification or “legacy style” from June 2 4, 20-19.
Beginning on June 17, 20-19, all API calls for Edits.images: that the upload will automatically employ the newest specification into the icon. Earlier June 17, 20-19, programmers should use the Play Console Migration dates are different for API consumers After June 17, 20-19, you should upload The specification that is new.