IdeaWell

Project ideas from Hacker News discussions.

F-Droid 2.0

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Theme 1: Praise for the F‑Droid 2.0 redesign
- outadoc: "Very cool, the visual redesign was very much needed and I had been using Droid‑ify for a while because of this. I'll switch back to the official app, congrats to the contributors!"
- zephiel7: "This is very good to see. Classic F‑Droid always seemed to fail at updating repos at least every week or so."

Theme 2: Reliance on alternative clients and multiple repositories
- szszrk: "Try F-Droid basic, it has this for a few weeks."
- someonebaggy: "Note it doesn't work very well, and Graphene recommends using Graphene's sandboxed Play Store instead."
- aorth: "I switched to Obtainium a year or so ago. I get all my apps from GitHub releases straight from the developers now."

Theme 3: Gaps in F‑Droid’s app catalog (proprietary/essential apps)
- juiceland: "For people who are die-hard F Droid users, do you get all your apps from it? I have tried in the past but it seemed like even when I restricted my use to basics it was missing things I needed to make my phone feel useful."
- HeatrayEnjoyer: "Store and restaurant apps, discord, streaming apps, most games, payment apps, apps for school, ride-sharing. I tried the 'degoogle' way and tossed after two days because that's impossible unless you're willing to adopt a more expensive boomer/millennial lifestyle."

Theme 4: Concerns about Google restrictions, sideloading lockdown, and interest in GrapheneOS
- jjice: "What does the future of something like F-Droid look like once Google does their lock down next year?"
- OutOfHere: "Once GrapheneOS ships on devices, it and Samsung can in time pick up where Android stops."

🚀 Project Ideas

RepoHub – Unified F-Droid/Aurora/Obtainium Frontend

Summary

  • A single Android app that aggregates F-Droid, Aurora Store, Obtainium, and custom repositories, deduplicates apps, handles background updates via the session installer, and verifies signatures.
  • Core value proposition: gives privacy‑focused users a reliable, up‑to‑date app source without juggling multiple stores or worrying about stale versions.

Details

Key Value
Target Audience Privacy‑conscious Android users, GrapheneOS adopters, power users who mix F-Droid with Play Store alternatives
Core Feature Unified repo list with automatic background updates, signature verification, and import/export of app selections
Tech Stack Kotlin, Jetpack Compose, WorkManager, Android Session Installer API, Room DB, Kotlin Coroutines
Difficulty Medium
Monetization Hobby

Notes

  • Commenters praised Droid‑ify’s UI but lamented unreliable background updates (e.g., “Gander5739: I've found Droid‑ify more reliable at doing background updates…”) – RepoHub would solve that with a verified session‑installer path.
  • Users asked for an easy way to add custom repos while keeping trust (e.g., “szszrk: F-droid allows that, you can have multiple repositories…”) – RepoHub provides a trusted UI for adding and verifying any repo.

fdroidctl – Cross‑Platform CLI for F-Droid Repo Management

Summary

  • A command‑line tool (with optional GUI front‑end) that lets developers and power users list, search, install, upgrade, and remove apps on an attached Android device using F‑Droid (or any compatible) repository indexes.
  • Core value proposition: brings the convenience of apt/brew to Android app management, enabling scripting, CI pipelines, and easy device‑to‑device sync.

Details

Key Value
Target Audience Developers, ROM maintainers, advanced Android users who administer multiple devices
Core Feature adb‑based install/upgrade/search with repo sync, signature verification, and export/import of app lists
Tech Stack Python (or Rust) with Click/Clap, android‑lib for adb, requests for repo fetching, optional Tauri/Electron GUI
Difficulty Medium
Monetization Hobby

Notes

  • Rom1v explicitly requested an F‑Droid “package manager client” on a computer that works via adb, showing clear demand.
  • Users like “aorth” who moved to Obtainium for GitHub releases would benefit from a unified CLI that can also pull from those sources, reducing friction when switching devices.

DroidTV – TV‑Optimized F-Droid Client

Summary

  • A lean Android TV app that presents F‑Droid (and compatible) repositories in a large‑icon, remote‑friendly layout, supports background updates via the session installer, and integrates with Obtainium for custom repos.
  • Core value proposition: makes it easy to install and keep open‑source media apps up‑to‑date on TVs without the frustrating cursor‑loss experience of the stock F‑Droid UI.

Details

Key Value
Target Audience Android TV users (e.g., Nvidia Shield, Onn boxes) who rely on F‑Droid for open‑source media, utility, or emulator apps
Core Feature TV‑focused UI (Leanback/Compose for TV), background update service, one‑click install from multiple repos
Tech Stack Kotlin, Jetpack Compose for TV / Leanback, WorkManager, Session Installer API, Room
Difficulty Medium
Monetization Hobby

Notes

  • AdmiralAsshat complained that “the cursor gets lost all the time” on TVs and that the UI is a nightmare – DroidTV directly addresses this pain point.
  • Users like “OutOfHere” already use Droid‑ify on phones; bringing a similar experience to TVs would earn community appreciation.

RepoSign – Trusted Signature Verification Service for Third‑Party Repos

Summary

  • A backend service and Android library that verifies APK signatures against repository metadata, provides trust scores, and alerts maintainers when a repo’s signing key changes or an APK fails verification.
  • Core value proposition: gives alternative stores (Obtainium, Droid‑ify, NeoStore) and end‑users confidence that apps from community repos are authentic and haven’t been tampered with.

Details

Key Value
Target Audience Developers of alternative app stores, Obtainium users, repo maintainers who want to offer verified F‑Droid‑style indexes
Core Feature API for signature verification, trust scoring, webhook alerts on key changes, Android library for client‑side verification
Tech Stack Backend: Node.js (or Python) + PostgreSQL; Frontend: React/Android Kotlin library; Deployment: Docker/Kubernetes
Difficulty High
Monetization Revenue‑ready: Subscription tiered (free public repo verification, $5/mo per private repo)

Notes

  • Several commenters raised concerns about trusting third‑party repos (e.g., “yjftsjthsd-h: I use F-Droid precisely because I don’t want that… cutting out the middleman is the opposite of what I want”) – RepoSign restores that trust while still allowing multiple repos.
  • The discussion about Obtainium version‑number mismatches and stale builds (“szszrk: …instantly got into issues…”) could be mitigated by automatic signature verification that flags when a newly fetched APK doesn’t match the repo’s signing key.

Read Later