Re:The Perils of Loading Native Libraries on Android
by Aqueous on Sunday November 08, 2015 @02:10PM
(#10529436)
Yes, I agree it is important and it is still also one of the last things you should think about. Certainly breaking the one-package-runs-everywhere by delivering different packages for different architectures in order to save disk space is one of the last things that should be considered. There are plenty of optimizations before this that you can make by compiling your native libraries differently, removing redundant information in resources, etc, before you should consider delivering architecture-specific APKs. And this is precisely because there are many back-channels for distributing APKs (back-channels which are also probably more commonly used in developing economies where those newer phones are unaffordable) in addition to the Play store.
Your friends with 700EUR phones aren't really all of the market and there's still enough devices out there that will not successfully install a 30+MB APK. And that's not even talking about how wasting users storage for things he doesn't need (just because you're a bit lazy) is just... wrong.