News for hackers. Stuff that matters.
Re:Saving Data: Reducing the Size of App Updates by 65% by iainmerrick on Wednesday December 07, 2016 @11:00AM (#13123483)
Yes, it definitely seems like fixing the flaws in the original APK design would be a win! Just signing the uncompressed data, as many others here have pointed out, would allow most of your suggestion to be implemented.

I wonder if it's a sign of communication problems between the Android and Google Play teams? The Play team seems to have spent years bending over backwards to build this really awkward solution, which could have been done a lot better with some low-level Android changes (i.e. a new APK format).

Re:Saving Data: Reducing the Size of App Updates by 65% by amluto on Wednesday December 07, 2016 @12:46PM (#13124460)
I bet there's a valid historical reason for the current design: APK looks a lot like JAR and Android is kind-of-sort-of Java. Java random-accesses its JARs, so the awkward format makes sense in the context. Android may, too, to a limited extent, but Android has no concept of running an APK in place, so it doesn't need this capability.
Re:Saving Data: Reducing the Size of App Updates by 65% by iainmerrick on Wednesday December 07, 2016 @02:27PM (#13125394)
Well, exactly, both APKs and JARs are just zipfiles with some extra conventions over format and contents.

Why not update the format? Android has been around long enough to make the advantages and disadvantages pretty clear.