5 ms·
Solving Android’s 65K Limit (Part 2): The Lollipop Generation – SafeDK Blog
- jreacher 11y agoLooking forward to the next part. :)
- shiraabel 11y agoThere's a new post up today on Reducing Your Method Count
- Asafsav 11y agoThe first part was great, this one is even better
- orlyshoavi 11y agoThanks for the post, proguard didn't help me so far
- Zigurd 11y agoThe biggest problem has been Google Play Services, but now, with Granular Dependency Support, you get only the packages you need. That means instead of nearly 30k methods, take it or leave it, you'll use up only a few thousand method table entries. In general, don't go nuts with big monolithic libraries. There's a lot of over-engineered Android code out there, especially when you have big, well-funded development teams. If your app still break the 64k limit, maybe you are stuffing too much into one app. Android makes it fairly easy for multiple apps to share data and other components.
- ronnies 11y agoGreat point. Take a look at the new post talking exactly about that: http://blog.safedk.com/technology/reducing-your-method-count-the-google-play-services-edition/?ref=hn http://blog.safedk.com/technology/reducing-your-method-count...