Resize bitmaps vs multiple Images folders for Android resolutions -

I am developing an Android app, but I am still experienced with some SDK stuff. One of those things is more than one resolution.

I know that the Android document talks about the use of multiple image folders for different screen resolutions. But I ask myself, how can I reduce my app size? And the place where I thought about changing the size of the images Also, I unpacked some apps and saw that they only used one folder for an image.

My questions are, should I resize my images or should I use multiple images for many folders? What is the difference? What do people usually do? What are the advantages and disadvantages?

I'm really thinking about getting the Android device density and shaping my image. But I do not know that this is a best practice.

The size of Android images is best to be missing in the appropriate folder. For quality you should always scale down , not above
So, if you use the highest resolution image in your folder, then it may be enough

It is better if you use the appropriate DPI for that resolution.: 480 dpi

---

for drawing-xxhdpi image is now the way to manage graphics.

I like to use as little images as possible, put ads in each folder (on every appropriate DPI, because I really dislike 72 dpi images) For example, To fill a background, I use tiled bitmaps instead of full size, which saves me lots of bits.

I also take advantage of gradients and layers

I also use drawables (which are scalable, because they are drawn on runtime ) And 9 patch (these people are selectively dragable).

And I take advantage of Unicode Glyph (some that support Android): They are scalable by definition, because they have a TTF Are part of the font

Sometimes I also use SVG graphics (which are vectorals), through the use of external libraries.
The other side of the medal is that you have a better image simpler, because they are stored in memory and you have to calculate the size in pixels when creating bitmaps from them.
And sometimes the library is not very fast and optimized, so it may be something to look like.

---

I think I have been quite logical, but I have given you a very rare idea about designing a UI which can be good but it is not necessarily heavy.