This screams for small, modular artifacts which can be composed! Most of the library’s offerings are very disparate, having only the fact that they’re by Google as a common thread.
You should want to put it in your applications and not have to worry about the overhead it brings. You’ll have a hard time making a compelling app that lives in the Google Play ecosystem without it. Like Guava it is also a monolothic library but it is a bad thing in this case.Ī lot of really cool functionality is being put in Play Services. Some of the services it provides are invaluable.
The monolith game play apk#
The Play Services library includes proprietary functionality built on the normal Android APIs and a separate APK downloaded on all devices with the Play Store. One third of the limit! Now that is scary. Google Play Services 5.0 which just launched contributes over twenty thousand methods to your app. 20% of this hard limit vanishes when you include Guava. The dex method limit is a hard 64k limit to which Guava contributes just over 14k methods. The latter is no longer a valid argument. In the world of Android the mention of Guava has a bit of a negative stigma due to the dex file format’s method limit and a concern about bloating APK size. Nobody thinks twice when bundling it for the JVM. Guava is a monolithic library, but that’s not necessarily a bad thing. Play Services 5.0 Is A Monolith Abomination
0 kommentar(er)
