If you are using PNGs, this should most definitely be in mipmap. This is because I’m using vector drawables. You’ll notice that the drawables are in the drawable directory. Let’s assume your Android Manifest’s tag has To add an adaptive icon that replaces those PNGs on API 26+ devices, you’ll add a res/mipmap-anydpi-v26/ic_launcher.xml file that looks like this: īy 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. Users will benefit from your work even as you work through other behavior changes. Note: you do not need to target API 26 to provide an adaptive icon - only compile against it. I’ll walk you through what it took to convert Muzei’s current icon into an adaptive icon. Talk to your designer before trying to force everything into vector drawables. Note: there are valid cases where PNGs are the correct choice for your app. 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. 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. This is really how you make a good first impression for users with Android O devices. 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. 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.
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.
0 kommentar(er)
