IdeaWell

Project ideas from Hacker News discussions.

Google removes "Doki Doki Literature Club" from Google Play

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

4 PrevalentThemes in the Discussion

Theme Supporting quote
1. Platform gate‑keeping & abrupt removals – Google/Apple are seen as pulling titles like Doki Doki Literature Club without clear rationale, reinforcing a top‑down curation model. > "In a few months Google will automatically deploy new software on our devices. This will be for our benefit and to help protect us." — kcb
2. Desire for true user control (sideloading) – Many users resent locked‑down app stores and view sideloading as a low‑friction way to retain freedom. > "Well, at least we can "sideload" this easily with minimum attrition, right?" — oceansky
3. Alternative payment infrastructures – The thread highlights non‑card systems (e.g., BLIK) that could break Visa/Mastercard dominance and improve transaction security. > "works for both" — gambiting (referring to BLIK code flow for online and in‑person payments)
4. Antitrust & open‑ecosystem arguments – Critics argue that a handful of corporations wield excessive power over software distribution and payments, calling for regulation and interoperable solutions. > "We need web‑based app installs without scare walls ("downloading from the internet is dangerous"), without hidden settings menus to enable them, and without any interference or meddling from the hyperscalers." — echelon

The summary keeps to four core threads, each backed by a direct quotation from the original participants.

🚀 Project Ideas

SideLoad Guard

Summary

  • A user‑controlled, sandboxed installer that lets Android users safely download and run APKs from any source, using time‑limited verification codes to prevent accidental installs. - Core value: restores true sideloading freedom without exposing users to malware or Google policy penalties.

Details

Key Value
Target Audience Android power users, developers, and tinkerers who want unrestricted app installation.
Core Feature Generate a 6‑second, single‑use verification token that must be entered on both the device and the source site; the token expires after first use.
Tech Stack Android Java/Kotlin, React Native front‑end, Firebase Auth for token distribution, Node.js attestation server.
Difficulty Medium
Monetization Revenue-ready: Subscription ($2.99/mo) for premium verification servers and analytics.

Notes

  • HN commenters repeatedly lament “We need to be able to sideload without Google meddling”; a token‑based system directly addresses that pain point.
  • Could be packaged as a simple Chrome extension + companion Android app, making adoption trivial and sparking discussion about policy reform.

Universal Microcode Pay (UMP)

Summary

  • A lightweight, cross‑platform payment layer that replaces fragmented local solutions (e.g., BLIK) with a universal 6‑digit merchant code that works both online and offline.
  • Core value: enables frictionless, anonymous micro‑transactions across borders without relying on Visa/Mastercard or nation‑specific payment processors.

Details

Key Value
Target Audience Small merchants, indie developers, and users in regions with limited payment infrastructure.
Core Feature Generate a cryptographically signed 6‑digit code per transaction; merchants verify via a public API before completing the sale.
Tech Stack Web (React), backend (Go + PostgreSQL), QR‑code generation library, optional native mobile SDKs (iOS/Android).
Difficulty Low
Monetization Revenue-ready: Transaction‑fee of 1.5% per payment (optional volume discount).

Notes

  • Payment‑processor commenters (gambiting, lxgr) want a universal, collision‑safe code; UMP provides a provably unique code with anti‑collision guarantees. - Would be attractive to EU/US users looking for alternatives to Visa/Mastercard and would spark debate on open payment standards.

OpenAppVerifier Network

Summary

  • A decentralized verification marketplace where developers can publish signed attestations of their apps, and users can verify authenticity without relying on Google Play or Apple App Store approval.
  • Core value: removes the gatekeeper bottleneck, letting any app be distributed securely while keeping the verification process transparent and community‑audited.

Details

Key Value
Target Audience Open‑source developers, privacy‑focused users, and regulators pushing back against app‑store monopolies.
Core Feature Upload an app bundle to the network; a smart contract issues an immutable verification hash and age‑rating metadata.
Tech Stack Ethereum (or Polygon) smart contracts, IPFS for storage, React.js front‑end, Rust backend for node operators.
Difficulty High
Monetization Hobby

Notes

  • Numerous HN posts (e.g., “Google can dictate who has or retains access’) argue that a decentralized verification layer would solve the monopoly problem.
  • A concrete, open‑source contract could be referenced in future antitrust discussions, making the project a rallying point.

Content Warning Engine (CWE)

Summary

  • An OS‑level content‑warning overlay that automatically surfaces granular warnings (e.g., self‑harm, violence) before launching any app, letting users customize trigger thresholds.
  • Core value: empowers users to control exposure to disturbing content without censorship, addressing concerns about “trigger warnings” and platform moderation overreach.

Details| Key | Value |

|-----|-------| | Target Audience | End‑users of Android/iOS, parents, and accessibility advocates. | | Core Feature | Parse app metadata + optional developer‑provided JSON warnings; present a pop‑up with opt‑in/out and a per‑warning “skip forever” toggle. | | Tech Stack | Android Service (Java), iOS App Group extensions (Swift), Electron overlay for desktop testing, JSON schema for warning standards. | | Difficulty | Medium | | Monetization | Hobby |

Notes

  • Commenters like “The warning was cited as an explanation as to why that game was delisted” show appetite for explicit warnings rather than outright bans.
  • Could be marketed as a privacy‑preserving alternative to heavy‑handed content removal, inviting discussion on user agency.

App Store Proxy Federation (ASPF)

Summary

  • A user‑run proxy service that aggregates multiple app stores (Google Play, Apple App Store, F‑Droid, third‑party repositories) into a single searchable interface, enforcing developer verification and age‑rating checks while bypassing walled‑garden restrictions.
  • Core value: gives users seamless access to any app while maintaining security and compliance, directly countering “gatekeeper” concerns.

Details

Key Value
Target Audience Mobile power users, developers seeking wider distribution, and advocacy groups.
Core Feature Query a unified API that returns app metadata from all stores; the proxy validates signatures and age‑rating tags before presenting results.
Tech Stack GraphQL gateway (Node.js), Dockerized store connectors (Google Play API, Apple Search Ads API, F‑Droid API), React Native front‑end.
Difficulty High
Monetization Revenue-ready: Freemium with premium “Verified‑Only” filter at $4.99/mo.

Notes

  • HN discourse repeatedly stresses “Google should not be able to remove apps arbitrarily”; ASPF offers a concrete technical workaround.
  • Could be positioned as a public‑good – an open‑source federated app marketplace – making it a natural topic for policy‑focused discussions.

Read Later