WinClean
WinClean copied to clipboard
5cover
Keep Specific "Useless App"
When removing useless apps, keep Xbox as it has become a large part of the windows system, it is needed for some games even on windows.
Thank you for reporting this. You're right. This is a mistake on my end. You can't just group a bunch of apps and call them useless. Not only is such an "all or nothing" approach mean to users who actually use/need any of those apps, it's also inhibiting the user's choices as they cannot choose specific apps.
I'm unsure how to fix this problem, but here are 3 possible solutions:
- Divide the "Remove useless apps" scripts into several, smaller scripts for each individual app.
| Pros | Cons |
|---|---|
| This will provide the user with more choices and control over the debloating process. | This will result in the introduction of numerous new scripts in the "Debloating" category. This might confuse or overwhelm the user. |
| This will allow for additional information in the script description, such as a description of the app, as well as potential concerns/issues regarding its removal. |
- Associate with the script an interface to select which apps should be removed.
| Pros | Cons |
|---|---|
| This would allow for customization of which apps to remove without cluttering the "Debloating" category with a bunch of new scripts | This would make the interface feel less consistent. |
- The first solution, but add the scripts to an "Apps" subcategory. This could be extended to introduce multiple subcategories: services, startup items, administrative tools, explorer settings... This solution would be part of a larger improvement in how scripts are categorized and organized.
| Pros | Cons |
|---|---|
| This would allow for a more precise categorization of scripts. "Maintenance", "Debloating" and "Customization" are pretty straightforward and embody the three tasks WinClean can assist you with, but they don't indicate what the individual scripts actually are about. |
I'm currently thinking about the third solution, but I'm open to additional input on this.
Honestly, I spent a solid minute clicking on the part where it shows what the script runs thinking I could change it, so maybe if you make it so it can be customisable via the textbox, that would be good.
The code is customizable for "custom" scripts added with the "Add scripts" button. "Default" scripts integrated with the app are read-only. Custom and default scripts are separated in two groups in the list view. I'm unsure how to make that distinction clearer.
I'm just a different kind of special, I don't read unless its in big bold letter saying warning
I should probably close this. If you have any other questions, feel free to let me know
Edit : I'm reopening this for version 1.4.0