4 ms·
This may be slightly off-topic, but as someone who has wanted to write apps before, I find the amount of "bloat" surrounding the Android ecosystem in general is
by userbinator 8y ago
This may be slightly off-topic, but as someone who has wanted to write apps before, I find the amount of "bloat" surrounding the Android ecosystem in general is astounding. For example, there is a "LegalTerm" app whose classes.jar is nearly 2MB, and I suspect its function is to only display this legal information and possibly ask the user whether to agree:
https://github.com/julKali/nokia8-evenwell/blob/master/packages/LegalTerm/apktool/res/values-en-rUS/strings.xml 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/packages/LegalTerm/apktool/res/drawable-xxxhdpi/abc_text_select_handle_left_mtrl_dark.png 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.
- Denvercoder9 8y agoIt's because of the Android Support Library (or AndroidX/JetPack nowadays). It is basically a backport of many features found in new Android versions to devices running older Android versions, and is embedded in (almost) all apps to make them work and look consistent across Android versions. It shows up prominentely in decompiled apps, but it's not found in the original source trees as it is added as one of the final steps during the build stage. No one actually implements text selection themselves.
- nikeee 8y agoIt has to be mentioned that the support library also contains exclusive components such as the ConstraintLayout. From my (very little) experience, it's basically impossible to ship an Android app without using anything of the support library.
- howard941 8y agoRegarding UI, the Android environment encourages layout customization for as many different permutations of display size and orientation your app's likely to encounter in the wild, easily a dozen? Despite the many layout adaptations suggested best practices would not include the use of multiple, large bitmaps. [0] https://developer.android.com/guide/practices/screens_support https://developer.android.com/guide/practices/screens_suppor... [1] https://developer.android.com/topic/performance/graphics/ https://developer.android.com/topic/performance/graphics/
- MithrilTuxedo 8y agoMultiple icons have been in Android since the beginning, and Apple started doing the same thing. If you navigate up a folder from your link, you'll see they also support dozens of languages in addition to devices of different sizes and pixel densities. 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_support.html 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-guidelines/macos/icons-and-images/app-icon/ 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.
- int_19h 8y agoFWIW, I'd say that Win10 display scaling is better than macOS, since you can use non-integer scaling factors. Linux used to be better still, with arbitrary scaling; but recently I've noticed that Gnome has also adopted the macOS model, which is really annoying on some display sizes, mostly on laptops (e.g. on Thinkpad X1, 1x is too small, and 2x is too large). For Macs it's more viable because they control the hardware, but there are some specific scenarios where it doesn't help - I remember this was a major problem when trying to hook up a Mac Mini to a TV a few years ago. 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.
- 8y ago
- kakwa_ 8y agoThe level of bloat in term of external calls can also be astonishing. This week-end I was analyzing an app of a classified advertising for buying/renting houses and condos. 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.