The secret? Don't use android app compat, or rather, don't use any external library. Just plain old java. The apps are ugly (no themes) but they work extremely fast and to the point.
The secret? Don't use android app compat, or rather, don't use any external library. Just plain old java. The apps are ugly (no themes) but they work extremely fast and to the point.
In case anyone else was wondering where to get such apps. Probably on F-Droid too?
This feels like the analog of the "10 GB node_modules" meme.
I wonder how much of the size explosion is due to feature bloat, inefficient implementation, backward-compatibility stuff, and external libraries...
Last time I checked it was a mix of assets (images mainly) and rarely used functions. In the case of app compat almost all is due to backward compatibility. That library allows you to use features intended for newer APIs, but making it compatible with older versions. This has advantages (mainly the themes) but it also means that the apps contains a lot of assets and code that will never run. The app bundle reduced this problem, but it's still present.