client icon indicating copy to clipboard operation
client copied to clipboard

Several Feature Requests

Open TotallyAvailable opened this issue 2 years ago • 1 comments

Is your feature request related to a problem? Please describe.

Option to hide Disabled Apps

  • Updating disabled Apps re-enables them, requiring manually disabling them again. -> No "update all" (worth mentioning, not used personally) -> Setting them to ignored is obviously a bad idea. -> The risk of overlooking stuff in-between.

Better Indication of Outdated Apps

  • A different color for outdated apps that can't be updated. Given that they get shifted upwards still in the "up-to-date" version color while needing manual action, something like a red ring around it would be greatly appreciated. Be it from apps shifting from Izzy to F-Droid (happens more often than you'd think) or using GitHub versions following identical version numbering.

Faster Repo Sync

  • Option to Sync multiple Repos in parallel while keeping the processing as is. Should massively speed up the "no changes" sync with bigger repo lists without breakage.

Transparency/Security feature

  • Option to be informed/warned if an (installed) app has been removed from the index.

Describe the solution you'd like

  • A simple toggle in the Settings menu for -> hiding disabled Apps -> indicating "non updatable" updates -> parallel syncing -> comparing current to last index, pointing out (installed) apps removed from the index/repo. <- probably the most "important" thing on the list while partially solving "Better Indication of Outdated Apps"

  • Alternatively giving disabled apps a lower sorting priority (always at the bottom in the list of available updates) with a slight shade/greyed out (?) appearance. Maybe even below a collapsible divider labeled "Disabled".
  • Or just changing the Update button to an Enable button (like the Play Store does it) telling "manual updaters" like me to pay a bit more attention to not visit sites for Apps I actively disabled.

TotallyAvailable avatar Jan 30 '24 06:01 TotallyAvailable

@TotallyAvailable how about one issue per ticket? else it is hardly possible to find, keep track or have a discussion about one particular issue. i'm also pretty sure therefore an implementation is more unlikely. e.g. i would :+1: one or another of your issues, but not all.

but please do not open duplicates! use existing issues and add your thoughts, suggestions, experiences etc.. why should a developer contribute hours or even days to implement a feature, if people don't even find it worth to take a few minutes to check for duplicates. ...and hence even wasting others time who sort out duplicates and keep the issue tracker tidy.

DJCrashdummy avatar Sep 13 '24 22:09 DJCrashdummy