nextcloud / nextcloud/android

Memory Optimization

Open
#17,640 0 comments 0 reactions 0 assignees View on GitHub
enhancement performance 🚀
Dominant language
Kotlin
Stars
5.6k
Forks
2k
Avg merge
2d 18h
Merged PRs (30d)
92

Description

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

[Document #1](https://android-developers.googleblog.com/2026/08/app-quality-memory-optimization-secure-onboarding.html?m=1)

[Document #2](https://android-developers.googleblog.com/2026/08/app-broader-memory-limits.html)

[Document #3](https://developer.android.com/about/versions/17/behavior-changes-all#app-memory-limits)

Things to-do:

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

@tobiasKaminsky CC

Contributor guide

Open the contributing guide

Research direction

Start by reading Documents #1–#3 to understand the Google Play memory requirements for Android 17. Then inspect the app’s DEX configuration and bitmap usage, and identify existing OOME reports or handling. Done means the DEX footprint and bitmap memory usage are improved and relevant out-of-memory issues are addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile, performance
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.