3 ms·
Last year I was invited to interview at Google Aarhus for a job on exactly this topic. We discussed fun, very simple ways to avoid including loads unused librar
by gergo_barany 9y ago
Last year I was invited to interview at Google Aarhus for a job on exactly this topic. We discussed fun, very simple ways to avoid including loads unused library code, and I was told that they already had some ridiculously efficient, practical way of compressing translation strings. I was there last November, and I had the impression that a lot of low hanging fruit would be picked off very quickly. Not sure what parts of this work actually shipped in these last 11 months. But work may still be ongoing.
- toast0 9y agoAt this point, I don't think there is anything simple you can do for translations in Android. Some of the translations are loaded outside of app context, and app developers may not know which ones those are. Allowing the files to be compressed in the apk would require support in the Android system, and there are a billion devices already shipped that don't know how to do that. If you can tell what strings need to be in the old way and what can be done differently, you could do any number of easy things to compress the strings that don't need to be accessible by the system.