Solving Android’s 65K Limit (Part 2): The Lollipop Generation

The 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.

Re: Solving Android’s 65K Limit (Part 2): The Lollipop Generation – SafeDK Blog

#7

Post by ronnies » Thu, Jul 02, 2015, 6:31 AM UTC

Zigurd wrote: post #6

The 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 tea…

Great point. Take a look at the new post talking exactly about that: http://blog.safedk.com/technology/reducing-your-method-count...