Project ideas from Hacker News discussions.

Keep Android Open

📝 Discussion Summary (Click to expand)

1. Android’s quality vs. iOS
Users repeatedly complain that Android is buggy and “mediocre” while iOS is “polished.”

“Android is not good. I use it despite its flaws, because of the trade‑offs, not because it’s better.” – stackghost
“I own a Pixel and while the hardware seems decent, I've had a buggy and annoying experience with Android, and it's been getting worse lately.” – stackghost

2. Google’s tightening of control
The move to lock down sideloading, bootloaders and Play Services is seen as a step toward a closed ecosystem.

“Google phones are not going to suddenly become luxury devices.” – stackghost
“Google’s plan to restrict sideloading… is a direct threat to independent AOSP distributions.” – fermigier
“Google’s moves are surprising… more to do with them embracing being a service player.” – StopDisinfo910

3. Security & privacy advocates push alternative OSes
GrapheneOS, e/OS, and other “de‑Google‑ed” builds are praised for their privacy‑first design.

“GrapheneOS is such a breath of fresh air.” – microtonal
“GrapheneOS is great!” – microtonal
“GrapheneOS only supports devices with isolated radios.” – microtonal

4. Banking & 2‑factor authentication forces mobile‑only
Banks increasingly require the native app for 2FA, making non‑Google/Apple phones unusable for many users.

“I use several US‑based banking apps… I’ve got a mix of well‑known national bank apps and smaller local credit‑union apps working.” – Pfhortune
“Banks are pushing mobile apps for 2FA.” – noughtnaut
“I use banking apps just fine on GrapheneOS.” – Pfhortune

5. The duopoly and lack of competition
Google and Apple are portrayed as monopolistic, stifling innovation and forcing users into a single ecosystem.

“Google killed every other competition via dumping and shady business practices.” – m4rtink
“The duopoly is a problem.” – 0x1ch
“Google’s moves are surprising… more to do with them embracing being a service player.” – StopDisinfo910

6. Freedom vs. convenience trade‑offs
Many users accept the inconvenience of a second phone or a more complex setup to preserve device freedom.

“I use it despite its flaws, because of the trade‑offs.” – stackghost
“I would have to carry a second phone.” – cwillu
“People will give up everything if it means avoiding the least bit of effort.” – raw_anon_1111

7. Regulatory pressure and the future of open ecosystems
EU and other regulators are being urged to enforce openness and prevent further lock‑in.

“I contacted the EU DMA team… got a real reply within 24 hours.” – ruuda
“We need legislation to enforce open ecosystems.” – 0x1ch
“The EU and every other nation with digital sovereignty concerns need to make this happen.” – 0x1ch


🚀 Project Ideas

Open Android Marketplace

Summary

  • Provides a decentralized, open‑source app store that bypasses Google Play’s verification and attestation requirements.
  • Enables users to install, update, and manage apps on any Android device, including those running GrapheneOS or other privacy‑focused ROMs.
  • Core value: restores true ownership of the device and eliminates the “Google‑only” app ecosystem.

Details

Key Value
Target Audience Android users on privacy‑focused ROMs, developers of niche apps
Core Feature Peer‑to‑peer signed‑app distribution with community reputation scoring
Tech Stack Rust backend, WebAssembly front‑end, IPFS for storage, OAuth‑like identity
Difficulty Medium
Monetization Revenue‑ready: subscription for premium analytics & support

Notes

  • HN users lament “Google‑only” app restrictions; this solves that pain.
  • Encourages a healthy open‑source ecosystem and reduces reliance on Google Play Services.

NFC Payment Bridge

Summary

  • A lightweight library that emulates Google Pay’s NFC host card emulation on non‑Google OSes.
  • Allows users to use contactless cards, transit passes, and payment apps on GrapheneOS, LineageOS, etc.
  • Core value: removes the “no NFC payments” barrier for privacy‑focused phones.

Details

Key Value
Target Audience Privacy‑focused Android users, developers of payment apps
Core Feature Open‑API NFC HCE wrapper with secure key storage
Tech Stack C++ core, Java/Kotlin bindings, OpenSSL, Android NDK
Difficulty Medium
Monetization Hobby

Notes

  • Addresses frustration that “Google Pay doesn’t work on GrapheneOS” (see microtonal).
  • Enables banking apps that rely on NFC to function on open ROMs.

Banking App Compatibility Layer

Summary

  • A runtime shim that satisfies banking apps’ Play Integrity and attestation checks.
  • Provides a virtual “Google Play Services” environment that mimics required APIs without exposing user data.
  • Core value: lets users run banking apps on non‑Google OSes without needing a second phone.

Details

Key Value
Target Audience Android users on custom ROMs, banks, fintech developers
Core Feature Play Integrity API mock, secure sandboxed environment
Tech Stack Kotlin, AndroidX, Binder IPC, Docker‑style sandbox
Difficulty High
Monetization Revenue‑ready: licensing to banks, subscription for support

Notes

  • Solves the pain point “banking apps refuse to run on non‑Google OS” (see 0x1ch, microtonal).
  • Could be offered as a library to ROM maintainers.

Phone Ownership Dashboard

Summary

  • A cross‑platform app that aggregates device ownership data: bootloader status, OS version, privacy settings, and hardware kill switches.
  • Provides actionable steps to unlock, secure, or revert changes, with safety warnings.
  • Core value: empowers users to understand and control their device’s lock status and privacy posture.

Details

Key Value
Target Audience Android users, especially those considering custom ROMs
Core Feature Device health audit, unlock/lock workflow, kill‑switch status
Tech Stack Flutter, Rust backend, Android Debug Bridge (ADB)
Difficulty Medium
Monetization Hobby

Notes

  • Addresses the “how to unlock bootloader” confusion and safety concerns (see 0x1ch, microtonal).
  • Helps users avoid bricking their phones.

Multi‑Device Banking Sync

Summary

  • A secure, open‑source service that aggregates banking data from multiple devices (phone, tablet, desktop) via OAuth and Open Banking APIs.
  • Allows users to access banking features on any device without installing a dedicated app.
  • Core value: eliminates the need for a phone‑only banking app, reducing reliance on Google Play.

Details

Key Value
Target Audience Users of banks that support Open Banking, privacy‑conscious consumers
Core Feature Unified dashboard, push notifications, two‑factor via TOTP
Tech Stack Node.js, PostgreSQL, OAuth2, TOTP, end‑to‑end encryption
Difficulty Medium
Monetization Revenue‑ready: freemium with premium security features

Notes

  • Responds to frustration that “banking apps are mandatory” (see 0x1ch, j_maffe).
  • Leverages existing Open Banking standards to avoid vendor lock‑in.

Open Source Mobile OS Installer

Summary

  • A graphical installer that automates flashing custom ROMs (GrapheneOS, LineageOS, /e/OS) on supported devices.
  • Includes safety checks, rollback options, and a curated list of verified device builds.
  • Core value: lowers the barrier for non‑technical users to switch to privacy‑focused OSes.

Details

Key Value
Target Audience Android users wanting to install custom ROMs
Core Feature One‑click flashing, device compatibility checker, backup/restore
Tech Stack Electron, Rust, Fastboot, ADB
Difficulty Medium
Monetization Hobby

Notes

  • Addresses the “flashing is hard” pain (see 0x1ch, microtonal).
  • Encourages wider adoption of open ROMs.

Privacy‑First Messaging Suite

Summary

  • A set of end‑to‑end encrypted messaging apps (chat, voice, video) that run on any Android device without Google Play Services.
  • Integrates with Signal protocol, uses WebRTC for media, and offers a unified contact list.
  • Core value: replaces WhatsApp/Telegram with privacy‑friendly alternatives on open ROMs.

Details

Key Value
Target Audience Android users on custom ROMs, privacy advocates
Core Feature Signal‑based encryption, WebRTC media, cross‑platform sync
Tech Stack Kotlin, WebRTC, Signal Protocol library, SQLite
Difficulty Medium
Monetization Hobby

Notes

  • Responds to the need for secure communication without Google’s ecosystem (see microtonal, 0x1ch).
  • Provides a ready‑made solution for users who otherwise rely on Google‑controlled apps.

Regulatory Compliance Toolkit

Summary

  • A platform that helps OEMs, ROM developers, and app publishers comply with EU DMA, GDPR, and other privacy regulations.
  • Offers automated checks for Play Integrity, data minimization, and open‑source alternatives to Google Play Services.
  • Core value: reduces legal risk and encourages open‑source adoption.

Details

Key Value
Target Audience OEMs, ROM maintainers, app developers
Core Feature Compliance audit engine, policy templates, reporting dashboard
Tech Stack Python, Django, Docker, static analysis tools
Difficulty High
Monetization Revenue‑ready: subscription for audit services

Notes

  • Addresses the “Google’s monopoly” concerns and the need for regulatory pressure (see 0x1ch, 0x1ch).
  • Provides a practical tool for the community to push for open alternatives.

Read Later