ImageConver · Day 16 · Platform icon guide
Android App Icon Sizes Guide
Choose Android launcher, adaptive, monochrome, and Google Play icon assets by separating installed-app resources from store-listing artwork. The current Android model uses density-aware resources and adaptive layers rather than one permanently rounded bitmap.
Jawaban langsung
Apa yang dihasilkan halaman ini dan di mana tempatnya
Choose Android launcher, adaptive, monochrome, and Google Play icon assets by separating installed-app resources from store-listing artwork. The current Android model uses density-aware resources and adaptive layers rather than one permanently rounded bitmap. This guide covers launcher identity and Play listing artwork. It does not replace Android Studio previews, OEM launcher testing, notification-icon guidance, splash-screen artwork, TV assets, wearable assets, or brand review.
Icon work is a delivery system, not a single resize. A platform may use the same identity in a store, launcher, notification, settings screen, browser tab, installed web app, shortcut, or operating-system search result. Each context can apply a different mask, density, cache, compositing rule, or validation step. The recommended icon system should therefore be treated as a tested derivative of an editable brand master.
Mulailah dengan karya seni sumber bersih. Pertahankan subjek utama tetap di tengah, hapus teks yang tidak perlu, hindari detail garis rambut, dan nilai desain berdasarkan ukuran tampilan sebenarnya terkecil. Jangan menambahkan penutup luar platform atau bayangan sistem ke sumbernya kecuali pedoman resmi saat ini secara eksplisit mengharuskan perlakuan tersebut. Pratinjau besar dapat menyembunyikan masalah yang terlihat jelas pada ukuran 16, 32, atau 48 piksel.
Dimensi file saja tidak membuktikan kebenarannya. Konfirmasikan ruang warna, perilaku alfa, jalur file, tipe MIME, metadata manifes atau katalog aset, deklarasi tujuan, penamaan, perilaku cache, dan presentasi perangkat sebenarnya. Pertahankan file sumber dan dokumentasikan pengaturan generator mana yang menghasilkan aset rilis yang ditinjau.
Alur kerja
Proses ikon empat langkah yang terkontrol
- 1
Periksa sumbernya
Start with a high-resolution editable master and identify installed-app versus store contexts.
- 2
Pilih pengaturan
Design adaptive foreground, background, and optional monochrome layers on the required grid.
- 3
Hasilkan aset
Generate legacy density resources only where the supported project needs them.
- 4
Validasi pengiriman
Validate Android Studio output, Play Console requirements, themed icons, and multiple OEM masks.
Kualitas visual
Kesesuaian, detail, transparansi, dan pengakuan
Pembingkaian dan bantalan
Mode Fit mengubah arti. Berisi menyimpan sumber lengkap dan dapat menambahkan latar belakang di sekitarnya; penutup memenuhi kotak dan dapat memotong tepinya. Padding berguna untuk tanda di tengah, tetapi jika terlalu banyak akan membuat ikon terlihat kecil. Bandingkan masker dan pratinjau kecil sebelum menerima nilai.
Detail berukuran kecil
Perampingan raster menghilangkan detail. Goresan tipis, penghitung kecil, tekstur fotografi, dan jenis huruf dapat kabur atau hilang. Ikon kecil terbaik sering kali berupa gambar yang disederhanakan daripada versi karya seni pemasaran yang diperkecil secara mekanis. Tinjau keluaran piksel sebenarnya pada skala 100%.
Perilaku latar belakang
Transparansi tidaklah netral. Browser, peluncur, toko, atau sistem operasi mungkin menggabungkan piksel transparan dengan warna yang tidak Anda pilih. Karya seni platform full-bleed harus menggunakan latar belakang yang disengaja dimana panduan mengharapkannya, sementara format seperti ICO mungkin sengaja mempertahankan alpha.
Kontras warna dan pengenalan penting di lingkungan terang, gelap, berwarna, dan bertema. Uji ikon di dekat ikon pesaing dan pada berbagai latar belakang. Pembuatan otomatis tidak dapat menentukan apakah suatu merek bersifat khas, dapat diakses, disahkan secara hukum, atau konsisten dengan aturan merek saat ini.
Batasan penting
Apa yang tidak dapat dijamin oleh pembuatan ikon otomatis
- OEM launchers can apply different masks and visual treatments.
- Android platform guidance evolves and project templates may generate resources differently.
- The Play listing icon does not replace installed launcher assets.
- A size table cannot evaluate brand clarity, contrast, accessibility, or small-scale legibility.
Kasus penggunaan
Dimana halaman ini cocok untuk produksi
Pengiriman produk
Plan resources for a new Android application.
Pekerjaan kompatibilitas
Modernize a legacy bitmap launcher icon.
Tinjauan kualitas
Separate a Play listing asset from packaged app resources.
Serah terima pengembang
Audit clipping and themed-icon readiness before release.
Pelaksanaan
Konfigurasi, caching, dan pemeriksaan rilis
Simpan file yang dihasilkan pada URL yang stabil dan sadar cache. Manifes atau deklarasi HTML yang mengarah ke file yang hilang tidak dapat diselamatkan jika PNG yang tepat ada di komputer pengembang. Verifikasi status HTTP, jenis konten, dimensi, byte file, dan perilaku asal yang sama atau lintas asal jika relevan.
Perlakukan file konfigurasi sebagai kode yang dapat ditinjau. Periksa setiap entri manifes, catatan katalog aset, nama folder, faktor skala, token tujuan, dan nama file sebelum penggabungan. Fragmen yang dihasilkan sengaja menghindari tebakan nama aplikasi, URL awal, pengidentifikasi bundel, warna tema, atau pengaturan proyek milik aplikasi sebenarnya.
Pembatalan cache memerlukan pemeriksaan rilis. Aplikasi web, browser, peluncur, sistem build, dan penyimpanan yang terinstal dapat mempertahankan sumber daya ikon lama. Gunakan jalur berversi atau kebijakan cache yang disengaja, bangun kembali aplikasi, instal ulang bila perlu, dan bedakan sumber daya lama dari sumber daya yang dibuat secara tidak benar.
Validasi geometri dan alur kerja. Geometri mencakup pemangkasan, zona aman, pemusatan, perlakuan tepi, dan kejelasan ukuran kecil. Alur kerja mencakup kontrol sumber yang benar, pengaturan berulang, konfigurasi platform, output build, penerapan, dan rollback. File yang menarik secara visual masih bisa gagal karena proyek mereferensikan nama file yang berbeda.
Decision framework
Build the icon set from requirements, not habit
Write down the supported operating systems, browser engines, application targets, project tooling, and distribution channels before selecting files. A list copied from an old blog can be internally consistent yet wrong for a current project. Official platform documentation and the project’s own build warnings are the controlling evidence.
Separate master artwork from delivery derivatives. The master remains editable and high resolution; platform files are reproducible outputs. Keep appearance variants and semantic layers distinct when the platform expects them. Do not ask a resize operation to invent foreground, background, monochrome, dark, or tinted design intent.
Use the table as a starting inventory, then remove assets the project genuinely does not consume and add only requirements supported by official documentation or validated target behavior. Every retained asset needs an owner, source, generation method, configuration reference, and test surface.
Run a release audit after integration. Confirm each generated file is present in the built package or deployed location, referenced by the correct metadata, served with the expected MIME type, and visible after a clean installation. Capture screenshots or build evidence for the supported target matrix.
Recheck guidance when platform tooling changes. Icon pipelines are unusually sensitive to new masks, appearance systems, asset-catalog formats, installation criteria, and store validation. Record the review date and do not present historical dimensions as timeless requirements.
| Asset | Working specification | Validation |
|---|---|---|
| Adaptive layers | 108×108dp foreground and background; essential logo within centered 66×66dp | Android Studio mask previews and real launchers |
| Legacy launcher | 48dp mapped across mdpi, hdpi, xhdpi, xxhdpi, xxxhdpi | Density resource selection |
| Google Play | 512×512, 32-bit PNG, sRGB, full square | Play Console validation |
| Themed icon | Dedicated monochrome layer | Supported Android versions and launchers |
Production checklist
Document the asset inventory and test matrix
Create an inventory before implementation. For each asset, record its platform context, logical purpose, pixel or point dimensions, scale factor, filename, source-art revision, background and alpha policy, configuration reference, and the application or browser that consumes it. This prevents two files with similar dimensions from being treated as interchangeable when their semantics differ.
Define a representative test matrix rather than checking only the developer’s primary device. Include the minimum and maximum supported operating-system versions, relevant density classes, at least one light and dark environment, required appearance or theme variants, and the installation or distribution channel. For web applications, include a clean browser profile and a reinstall after cache changes. For native applications, include a release-style build rather than only an editor preview.
Review small contexts independently. Open exported pixels at 100% scale, place them beside typical neighboring icons, and check silhouette, contrast, edge clarity, and recognition without relying on the app name. Record defects against the editable master so the next iteration changes the design source rather than painting corrections into generated derivatives.
Keep generation reproducible. Save the approved master, generator version or script, settings, official references, review date, and validation evidence together. Checksums can identify the exact files reviewed. If a platform rejects or transforms an asset, preserve the rejection message and resulting presentation because that evidence is more useful than guessing from a generic size list.
Plan maintenance ownership. Someone must recheck platform documentation, build warnings, installation behavior, and store validation when supported targets or tooling change. Retire obsolete files only after proving they are no longer referenced by source code, manifests, asset catalogs, deployment templates, cached application data, or release automation.
Pribadi
Pemrosesan lokal dan penanganan aset
Browser membaca sumber yang dipilih dengan API file lokal, menggambar turunan ke kanvas, mengkodekan data PNG, dan menyusun ZIP atau ICO yang diminta dalam memori. ImageConver tidak mengirimkan piksel sumber ke titik akhir konversi ikon dalam alur kerja ini.
Pemrosesan lokal mengurangi paparan transfer tetapi tidak membuat perangkat bersama menjadi pribadi. Unduhan browser, daftar file terbaru, folder tersinkronisasi, cadangan, ekstensi, dan pratinjau sistem operasi mungkin menyimpan salinan. Gunakan tempat kerja yang disetujui untuk merek yang belum dirilis atau karya seni produk rahasia.
URL objek yang dihasilkan bersifat sementara dan dicabut ketika diganti atau disetel ulang. Pindahkan aset yang telah ditinjau ke penyimpanan proyek terkontrol, pertahankan master yang dapat diedit, dan tutup tab setelah menangani materi sensitif.
Pertanyaan umum
Android App Icon Sizes Guide FAQ
What is the adaptive icon canvas?
Android guidance uses 108×108dp foreground and background layers, with essential logo content kept within the centered 66×66dp safe region.
What are the legacy density sizes?
A common 48dp launcher icon maps to 48, 72, 96, 144, and 192 pixels for mdpi through xxxhdpi.
What size is the Google Play icon?
Google Play specifies a 512×512 32-bit PNG in sRGB with a maximum file size of 1024KB.
Do I add rounded corners and shadows?
Do not add the outer Play mask or platform shadow. Google Play and launchers apply presentation treatments.
What is a monochrome icon?
It is an optional single-color layer used for themed icon presentation on supported Android versions and launchers.
Are adaptive icons only PNG files?
No. Adaptive icons are defined from foreground and background drawables, which may be vector or bitmap resources.
How should I verify the pack?
Use Android Studio tools, inspect generated resources, install test builds, and review multiple densities, masks, themes, and launchers.
Referensi utama
Dokumentasi platform saat ini
- Android Developers: Adaptive icons
- Android Studio: Create app icons
- Google Play icon design specifications
- Android Developers: Density buckets and units
Terakhir ditinjau: 20 Oktober 2026. Persyaratan platform dan perubahan alat; memverifikasi aset penting rilis terhadap dokumentasi utama saat ini.