Project ideas from Hacker News discussions.

Android’s new sideload settings will carry over to new devices

📝 Discussion Summary (Click to expand)

Three dominant themes inthe discussion

Theme Core idea Illustrative quote
1. Google’s “concession” is a thin‑veiled attempt to keep control The new 24‑hour wait is presented as a win, but it’s really a small, self‑serving gesture that still forces users through Google‑controlled gates. “Google’s latest concession makes the side‑loading controversy a big nothingburger.” – schubidubiduba
2. Desire for FOSS‑centric, root‑able alternatives Many users stress that real freedom means avoiding Google Play entirely, using F‑Droid, GrapheneOS, or other custom ROMs, and relying on ADB to bypass the delay. “If you don’t have the framework, you don’t have to worry about any of this (you also don’t get the benefits, bank apps that require validated OS, tap to pay etc, without the framework).” – fluidcruft
3. Scam narrative used as a pretext for tighter lock‑downs The “security” rationale is viewed as a convenient excuse to curb sideloading; users point out that scams also proliferate inside Play and that the restriction mainly limits legitimate users. “How long before there is a ‘we’ve detected your account has been used multiple times to re‑setup a phone… we’ve re‑enabled the Google Nanny Safety mode… also we’ve locked your Google account just in case…’” – xt00

The summary is intentionally concise, focusing only on these three recurring positions and backing each with a directly quoted remark from the discussion.


🚀 Project Ideas

[InstantSideLoad]

Summary

  • A lightweight CLI/GUI tool that lets users bypass Google’s 24‑hour wait by automatically signing APKs via ADB and pushing them to a connected device.
  • Eliminates the friction of manual sideloading while preserving the “once‑per‑device” verification rule.

Details

Key Value
Target Audience Power users, ROM/Custom ROM maintainers, developers who frequently install APKs outside Play Store
Core Feature One‑click generation of signed APKs, ADB push, and automatic handling of Google’s “wait‑day” token using a local attestation emulator
Tech Stack Python (CLI), Flutter (GUI), libadb, OpenSSL for signing
Difficulty Medium
Monetization Revenue-ready: $4.99 one‑time license for commercial use; hobbyists can use free tier

Notes- HN commenters repeatedly asked “how can you carry over without Play Services?” – this tool sidesteps that by handling verification locally. - Could be bundled with F‑Droid as the default installer, turning a pain point into a seamless workflow.

  • Potential for integration with web‑based “install‑from‑URL” services to help non‑technical users.

[F-Droid AutoSync]

Summary

  • A background service that syncs F‑Droid repositories, auto‑updates apps, and aggregates security notifications, removing the multiple “Update all?” dialog boxes.
  • Provides a unified, non‑Google update experience for users who rely on open‑source app stores.

Details

Key Value
Target Audience FOSS enthusiasts, privacy‑focused users, developers maintaining multiple F‑Droid repos
Core Feature Continuous background checking, silent batch updates, and push notifications for critical security patches
Tech Stack Rust (service), Electron (desktop UI), SQLite for repo metadata
Difficulty Low
Monetization Hobby

Notes

  • “Installing updates becomes an obnoxious process” – this service smooths that out, directly addressing the frustration in the thread.
  • Could be packaged as a system tray app that integrates with Aurora Store, giving non‑technical users a polished experience.
  • Opens a discussion on sustainable funding for FOSS app stores via optional “pay‑what‑you‑want” tier for premium sync features.

[DeviceAttestKit]

Summary

  • A desktop application that generates offline device attestation reports (including bootloader state, Google Play Services presence, and OS integrity) without needing a Google account, enabling users to satisfy banking or payment app requirements.
  • Turns an opaque Google‑only verification step into a transparent, user‑controlled process.

Details

Key Value
Target Audience Users of custom ROMs, privacy‑centric Android enthusiasts, developers needing attestation for legitimate services
Core Feature One‑click generation of signed attestation JSON that can be exported to apps or services requiring device trust
Tech Stack Go (backend), Qt (GUI), libsrtp for secure signing
Difficulty High
Monetization Hobby

Notes

  • “Do you run a custom ROM? I can’t imagine bothering with the hassle…” – this kit removes the hassle by providing an easy‑to‑share attestation file.
  • Addresses concerns about “carry over” status and the need for a Google account to prove device legitimacy.
  • Sparks conversation on alternative trust models and could be adopted by community projects like GrapheneOS as an officially endorsed tool.

Read Later