From my (very little) experience, it's basically impossible to ship an Android app without using anything of the support library.
The resources are done like that so the system doesn't have to scale icons -- so you don't see fuzzy icons anywhere because they've been scaled by the CPU. See: https://developer.android.com/guide/practices/screens_suppor...
It's worth noting that the Android apps installed on your device don't typically include all those icons. There are usually a handful, if not dozens of APKs that are available for download for apps when you get them from the Play store. The gradle build tool makes it relatively trivial to produce multiple versions of the same app, based on display size, display density, target Android version, and architecture. I can have resources for three densities, three device sizes, two OS versions, and two architectures, and produce 36 APKs from my build.
Apple did a similar thing with Universal Binaries back in the day that could run on PowerPC and x86.
Apple OSX has had scaling icons for a while too. You can define your icon in SVG (Android/iOS support this now) which is infinitely scalable, but generally icons are actually multiple images and the system selects the most appropriate one: https://developer.apple.com/design/human-interface-guideline...
This is all for systems that support display scaling and multiple architectures. Windows is still catching up.
The main complaint here, though, isn't that there are multiple zoom levels of the same icon, but that it's shipped with the app, instead of being provided by the OS.
Also, which non-rolling Linux distros have picked up 3.32 already? Ubuntu is supposed to ship 19.04 with it this April, but that's the closest one I can think of.
[0] https://developer.android.com/guide/practices/screens_suppor...
[1] https://developer.android.com/topic/performance/graphics/
The app makes quite a fair amount of calls to recover the ads from their REST API. But the vast majority (2/3 to 3/4) of calls are for external tracking services.
When an app is spending more resources and time tracking users than delivering useful content, it's kind of frightening.
https://github.com/julKali/nokia8-evenwell/blob/master/packa...
Yet looking at the other files included, it seems this app also draws its UI using bitmaps in a dozen different sizes, and has to reimplement something as elementary as text selection ( https://github.com/julKali/nokia8-evenwell/blob/master/packa... ). Are they going overboard, or is this just how Android works? I primarily work in Win32 and such a simple app there would have a size measured in kilobytes, not megabytes.