0x192 / 0x192/universal-android-debloater

Cater to diverse reasons for debloating - Add tags to filter by Performance/Privacy etc.

Open
#356 2 comments 3 reactions 0 assignees View on GitHub
enhancement
Dominant language
Rust
Stars
19.9k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

To minimise any impact while debloating, I would like to ONLY disable apps with high resource usage, above a certain threshold. Other apps maybe running in the background, but if it doesn't affect my battery life, I don't think it's worth the risk or to disable. Because if something breaks, I will need to re-enable everything just to be sure.

Ther's many reasons for debloating,
1. Performance - CPU (More concerned about this, since it will affect battery life)
2. Performance - RAM (Doesn't matter that much as long as you have enough ram)
3. Privacy
4. Disable unused apps, that are visible in the app drawer. Avoid clutter.

It would be great, if we can add a dropdown list to filter the above. Maybe a tag makes much more sense so we can filter "Recommended" list + "Performance - CPU" tag.

![image](https://user-images.githubusercontent.com/681355/185730578-1c0ec7f6-d9f1-498b-840d-2b99706c841f.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue suggests adding tags (Performance/Privacy) to filter apps in the GUI. Start by exploring the codebase for how app lists are currently structured and displayed. Look for UI components that handle filtering or tagging. Understand how app metadata is stored and how new tags can be integrated. Check existing tests for UI changes to ensure the feature works correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, rust
Domain
cli, mobile, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.