nailing down the F-Droid direction

So I've been a bit MIA on this, too many things hit me at once in the past few months. I've been working non-linearly on this, now I want to nail down the plan for the rest of the time.

Based on various discussions, it seems that the various offline use cases are the most interesting to focus on, like the Cuban app store. Here's my sketch of the work points so far:

smooth out swap
• harmonize user experience with Viento projects and Android Go
• automate as much of the process as possible
• work with SD cards
• index El Paquete for rapid access

offline malware tools
• many devices are out of date, don't get updates
• scan for exploits when adding to collections
• increase visibility by making F-Droid Nearby app for Google Play

conserve
• only load graphics/screenshots on wifi or sneakernet, not on metered connections
• battery conservation through Android schedule tricks
• pre-crunch/optimize all images that are added to F-Droid app repositories

How does this sound?
@cstiens @n8fr8

No files, tests, or entry points are named. Start by reviewing the proposed areas—swap, offline malware tools, and conservation—and resolve which direction is in scope with the maintainers; the issue does not yet define a concrete completion condition.

Written by the indexing model from the issue text.