Skip to content

Memory Optimization #17640

Closed

Description

@alperozturk96

Google Play is introducing a new quality requirements: reducing app memory footprint.

Document #1

Document #2

Document #3

Things to-do:

  1. Optimize DEX code
  2. Analyse and improve Bitmap memory usage
  3. Check OOME and fix them

@tobiasKaminsky CC

Activity

  1. moved this to 🧭 Planning evaluation (don't pick) in 🤖 🍏 Mobile clients teamon Sep 14, 2026
  2. PhilLab commented on Sep 23, 2026

    @PhilLab
    Contributor

    I think a crucial requirement here will be that we keep the released app supportable. Specifically the crash logs added to Github tickets, will become obfuscated and thus unreadable.

    We need to retain the mapping files (from obfuscation back to code)

    • for all released builds (gplay, fdroid, huawei)
    • and for every released version
    • Somewhere accessible, also to the community, so they can help with triaging

    And even if we retain the mapping files, it will still be a real pain to triage the Github log excerpts. Not only will you not see familiar bugs at a glance, but you also need to painstakingly retrieve the exact matching mapping file, and de-obfuscate it. This adds at least +5 minutes of work before you can even start the actual investigation.

    @alperozturk96 @tobiasKaminsky

  3. linked a pull request that will close this issue Enable app optimization with R8 #17699on Oct 12, 2026
  4. linked a pull request that will close this issueperf(bitmap): recycle #17786on Oct 12, 2026
  5. moved this from 🧭 Planning evaluation (don't pick) to ☑️ Done in 🤖 🍏 Mobile clients teamon Oct 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementperformance 🚀Performance improvement opportunities (non-crash related)

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions