Android manifest round icon

Адаптивные значки

В Android 8.0 Oreo появилась поддержка адаптивных значков.

Для работы с адаптивными значками следует использовать API 26 и выше. Адаптивные значки состоят из двух слоёв: фон и основная часть.

В манифесте по-прежнему остаётся старая запись о значке.

Далее следует создать файл res/mipmap-anydpi-v26/ic_launcher.xml. Android Studio 3.0 генерирует подобный файл, можете изучать его.

Слои содержат векторные изображения VectorDrawable. К слову сказать, в качестве фона можно использовать просто цвет.

Для передней части значка можно использовать PNG-файл (используйте ресурсы mipmap).

Для совместимости с Android 7 вы должны также создать ещё один файл ic_launcher_round.xml с таким же содержанием.

Если изучить ресурс для фона, то можно заметить, что для значка используются размеры 108dp*108dp. Основной слой значка имеет те же размеры, но нужно учитывать одно обстоятельство — фоновый слой работает как маска, накладываемая на передний значок. Поэтому вы должны проследить, чтобы маска случайно не закрыла важные детали значка.

Гарантировано будет виден центр значка 66dp, а 77dp применимо к общему размеру значка.

Адаптивные значки можно применить к App Shortcut.

На эмуляторе следует выбрать устройство Pixel и включить у него режим разработчика. Далее в настройках домашнего экрана появится пункт Change icons shape.

Дополнительное чтение

Implementing Adaptive Icons – Google Developers – Medium — в статье приводится пример применения линейного градиента для тени.

Releases · nickbutcher/AdaptiveIconPlayground — приложение с открытым исходным кодом для удобного просмотра эффектов значков с настройками.

Источник

Android Adaptive Icons

Deliver an eye-catching first impression by making your Android icon pop

• Jimmy Morales, Senior Developer, Guatemala

Adaptive icons are definitely not a new thing in the Android world. They were introduced in Android 8.0 (Oreo), around four years ago. Not so many things have changed since then, but I think it will be good if we do a quick review on the topic.

Legacy Icons

Let’s talk about how icons were implemented in versions prior to Oreo, which we will call legacy icons from now on. Legacy icons are easy to implement. You need to have at least one PNG for each different density from mdpi to xxhdpi (four in total), but ideally you should also add one for the xxxhdpi. The icon’s size needs to be 48×48 dp and it can have any transparency. This opens the opportunity to have icons with different types of shapes. It means your icon can be a circle, square, or any shape really.

Initially having a unique shape was a good practice because it meant your app icon was more likely going to stand out compared to other apps. But this resulted in a Launcher full of icons with different shapes and sizes and a lot of inconsistency.

Normalizing icon shapes and sizes

This started a new movement on trying to normalize the icons shapes and sizes in the Android Platform. Samsung was the first OEM that introduced a background behind the icons that make them look more consistent.

Left: Standard icon look. Right: Icons with backgrounds. Source: cnet.com

The second attempt at trying to introduce a more consistent icon experience was in Android 7.1 (Nougat) with the introduction of the roundIcon . This new feature had some restrictions, especially with OEMs looking to differentiate their devices by having different icon shapes (ie: Pixel devices use circular icons, Samsung a rounded square shape, other OEMs might use a rectangular shape). This was solved in Android 8.0 with the introduction of Adaptive Icons.

So… Adaptive Icons

An Adaptive Icon is made up of two layers, a foreground and background, both of 108×108 dp. Ideally these two layers should be vector assets, but they can also be PNGs. The downside of using PNGs is that you will need to provide at least 4 different PNGs per each density (mdpi to xxhdpi) for each layer (8 PNGs in total). With vector assets you will only need two files which will save you a lot of space.

Basically, Android will apply a mask to both layers and clip an area around your icon. Different OEMs will apply different shapes of masks. You need to have in mind that because of the applied mask you will need to put your icon in a safe area that is around 33dp from the center of the icon.

How to create an Adaptive Icon?

If you are a developer (with no design skills like myself) the short answer is to use the Asset Studio from Android Studio. Using Asset Studio is very easy, you can import both of your layers and the Asset Studio will generate the files for you.

The Asset Studio will show you the safe zone and a really nice preview on how different masks will be applied to your icon. You can resize both of the layers if needed. The background layer can be just a color drawable, but as I mentioned before you can also provide a vector asset, that means the background can be really anything, for example, you can have a gradient as the background layer.

When creating the Adaptive Icon, Asset Studio will generate for you several files. It will add the two layers as drawables, for example, if you used vector assets for your layers it will generate a drawable/ic_launcher_foreground.xml for your foreground layer and a drawable/ic_launcher_background.xml for your background layer.

The Adaptive Icon file by default will be called ic_launcher.xml . If your app’s minimum SDK is 26 or higher this file can live in the mipmap resource directory, but if not (most of the apps), it will be stored in the mipmap-anydpi-v26 resource directory. This is because Adaptive Icons are only supported on API level 26 or higher, and on versions below 26 you will need to have the legacy icon saved in the mipmap-mdpi , mipmap-hdpi , etc.

For example, if your minimum SDK is 23 you could end up with this file tree in your res directory:

If the ic_launcher_round adaptive icon is the same one as the normal ic_launcher , instead of duplicating the file you can provide a resource alias in your values-anydpi-v26 folder.

Now you only need to specify the icon file in your app’s AndroidManifest.xml like you would normally do.

And this is how the Adaptive Icon looks internally. It is pretty simple, you only need to use the adaptive-icon tag and inside add both layers using the background and foreground tags (Asset Studio does this for you).

For designers

If you are a designer and like to use fancy design tools, you can also use these tools to design Adaptive Icons.

More Adaptive Icon stuff.

The real reason for having two layers is because it allows OEMs to do really cool animations when an user interacts with your icon, like moving the foreground layer on top of the background layer.

But, how can we test the animated visual effects of our Adaptive Icons in a real device? Well, thanks to Nick Butcher again, we can use his Adaptive Icon Playground app to see how the animated visual effects perform in the icon. You can download the APK from the repo, run the app and you will be able to see the Adaptive Icons of all of your installed apps in your device.

Wrapping up

Implementing Adaptive Icons is a great way to make your app follow the best practices and is in tune with the other apps on the devices of our users. Remember that App Icons are a great investment because they usually are the first thing the user sees, and that also involves seeing the animated visual effects in the latest Android versions or supporting different Icon shapes in different OEMs.

At the time of writing this article, Android 12 is in beta, but hopefully when it gets stable in the next month I’ll update the article if we get something new.

Special thanks to Chris Weathers, Camilo and Mauricio for reviewing this.

Источник

Android manifest round icon

Круглые иконки приложений стали стандартом с момента появления Android Nougat 7.1 и нового компонента Pixel Launcher. Google даже ввел новый API, позволяющий разработчикам задавать круглую иконку для лаунчеров, которые это поддерживают. Что, безусловно, очень полезно в том случае, если у Вас сильный брендинг и Вы просто желаете сделать так, чтобы для лучшего соответствия новому лаунчеру иконка приложения показывалась круглой. Давайте рассмотрим несколько примеров обновленных иконок, у которых сильный брендинг и которые теперь имеют новый круглый значок для Nouget 7.1:

Некоторые значки расположены внутри белого круга с небольшой тенью, в то время как другие увеличены, с тем чтобы на них было показано больше деталей. Круглой иконке вовсе не обязательно становиться абсолютным кругом, как вы можете видеть на примере значка калькулятора. Благодаря интеграции новых круглых иконок в приложения можно гарантировать, что они согласуются с большинством приложений, уже установленных на устройстве пользователя. Кроме того, можно сохранить существующую иконку приложения, и она будет по-прежнему показываться на старых устройствах. И самое замечательное: весь процесс установки занимает всего несколько минут.

Создаем круглый значок

Android Asset Studio просто набита «лакомствами» для разработчиков, и в их числе возможность создания иконок для панели действий, вкладок, уведомлений и лаунчера, которые получаются с правильным разрешением для каждого возможного дисплея. Сперва давайте обратимся к Launcher Icon Generator, загрузим туда существующую иконку и выберем Circle shape, с тем чтобы создать новую круглую иконку. Я выбрал подходящий синий фон и увеличил иконку на 5%, чтобы сделать ее полной.

Затем нажмите на кнопку Download .ZIP, с тем чтобы скачать новую иконку, которую можно будет извлечь из архива и добавить в папку mipmap под Resources:

Нацеливаемся на Android API 25

Чтобы иметь возможность добавлять круглые иконки к нашему Android Manifest, мы должны убедиться в том, что запустили сборку Xamarin, которая поддерживает Android 7.1 (см пост здесь), а также в том, что мы обновили компилятор Android и установили целевой API на API 25 в настройках проекта:

Обновляем атрибуты Activity

Мы должны указать местоположение нашего Activity, у которого свойство MainLauncher установлено на значении true. Как правило, это MainActivity или кастомное SplashActivity, подобное тому, которое сейчас есть в моем приложении. Наряду с атрибутом MainLauncher и другими, такими как Label и Icon, которые отображаются. Мы можем просто добавить еще один атрибут с именем RoundIcon и установить в его значение нашу новую иконку. Мои атрибуты Activity выглядит следующим образом:

Источник

VectorDrawable Adaptive Icons

So the Android O APIs are final — API 26 is here! That means you can start compiling with API 26 right now (and you should really always compile with the latest SDK) as well as work towards targeting API 26.

One of the first things you should consider working on is providing an adaptive icon — an icon made of a separate background and foreground layer. This new format provides a consistent shape across all icons on a device and will also allow launchers to add visual effects by animating the background and foreground separately. This is really how you make a good first impression for users with Android O devices.

With the system handling the outer edge shape and its shadow, adaptive icons give you a chance to re-evaluate how you build your app icon. If you’re able to build your app icon as an SVG/vector image, consider avoiding bloating your app with more PNGs for the background and foreground and take advantage of VectorDrawables for your adaptive icon.

Note: there are valid cases where PNGs are the correct choice for your app. Talk to your designer before trying to force everything into vector drawables.

I’ll walk you through what it took to convert Muzei’s current icon into an adaptive icon.

Note: you do not need to target API 26 to provide an adaptive icon — only compile against it. Users will benefit from your work even as you work through other behavior changes.

The basics of adaptive icons

By placing it in the mipmap-anydpi-v26 folder, the resource system will use it in preference over any files in the other dpi folders (exactly what you want, since this file is replacing all of them) and that it should only be used in API 26+ devices.

You’ll notice that the drawables are in the drawable directory. This is because I’m using vector drawables. If you are using PNGs, this should most definitely be in mipmap . Another option is use a color resource for your background:

Round icons

For those of you with an android:roundIcon , you must keep that attribute to continue to support API 25 devices. Devices with round masks will use your custom roundIcon if available, but it is strongly suggested to use a single adaptive icon for those devices as well (this ensures you get the standard shadow, support for visual effects, etc).

I find this easiest by creating an alias resource. You’d keep your ic_launcher_round images in the res/mipmap directories for API 25 devices, but add a file in your values-anydpi-v26 folder:

Building a VectorDrawable Background

The background is a great place to start. Being a full bleed 108 x 108 dp image, there’s not much special about this one:

Just keep in mind that due to the masking of the image, users will usually only see the middle 72 x 72 dp.

Building a VectorDrawable Foreground

The foreground image, on the other hand, offers a unique challenge.

First, you have to handle creating the foreground shape itself. It is still on the same 108 x 108 dp artboard, but the ‘safe zone’ of what you know will be shown is only a middle circle of radius 33 dp — don’t put anything critical outside of that part!

Where I initially got stuck was when it comes to the traditional 45º material cast shadow that the foreground also needs to include. Normally, this would be where you’d have to break out the PNGs to get that perfect gradient. But gradient support was added to VectorDrawables back to API 24!

Getting gradients working, however, required a bit of research. The VectorDrawable docs point out the ability to use a GradientColor , but where to find a good example? On StackOverflow of course.

Now, Roman Nurik, the maker of the original Muzei icon, had made a fantastic SVG version of the launcher icon including the shadow as a
element in the SVG. I won’t pretend that I know how he came up with the correct values — talk to your local designers or read the material design guidelines for product icons a couple hundred times.

But what it became was a res/color/ic_launcher_shadow.xml file that looks like this:

You’ll note all of the attributes from the GradientColor documentation available to customize this to be just right.

Note: As of Android Studio 3.0 Canary 3, Android Studio flags gradient as an error (‘Element gradient must be declared’). It still works.

Now, we can refer to our gradient color the same way you’d refer to a color: with @color/ic_launcher_shadow in the VectorDrawable . In Muzei’s case, this means that the foreground background consists of two paths: the shadow and then the shape below it:

Note: this is also how you’d add a finish layer to your icon — a separate gradient above your shape as explained in the material design guidelines.

All the benefits, none of the APK bloat

By taking advantage of API 24’s addition of gradients to VectorDrawables, we can build well designed VectorDrawable adaptive icons that have the correct material shadows on foreground elements without resorting to adding even more PNGs into the app.

If you want to see it in action, join Muzei’s open beta, then download Muzei on an Android O Dev Preview 3 device and check out the commit that added the adaptive icon. (Although unless you have the superhuman ability to visualize VectorDrawables like Nick Butcher, you might find the full commit doesn’t add much over the code we already covered.)

For further information, you might want to check out Nick Butcher’s excellent series of articles on adaptive icons.

Источник