TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

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

16 pointsby shiraabelalmost 10 years ago

4 comments

Zigurdalmost 10 years ago
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&#x27;ll use up only a few thousand method table entries.<p>In general, don&#x27;t go nuts with big monolithic libraries. There&#x27;s a lot of over-engineered Android code out there, especially when you have big, well-funded development teams.<p>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.
评论 #9817196 未加载
jreacheralmost 10 years ago
Looking forward to the next part. :)
评论 #9807311 未加载
orlyshoavialmost 10 years ago
Thanks for the post, proguard didn&#x27;t help me so far
Asafsavalmost 10 years ago
The first part was great, this one is even better