Project ideas from Hacker News discussions.

GrapheneOS' rewritten Messages app is released

📝 Discussion Summary (Click to expand)

1. Desire for RCS and concerns about its implementation
Many commenters discuss whether the new GrapheneOS Messages app will support RCS, noting both the user benefit and the technical difficulty.
- “Does it do RCS?” – mewse‑hn
- “No. RCS is still quite hard to actually implement. There's an open issue for it but the effort is mildly herculean.” – OneDeuxTriSeiGo
- “If it can be done, GOS is in the best position to make it happen, and without RCS, chatting with normies is both extremely inconvenient … and categorically insecure.” – sicktriple
- “I hope RCS can die fast. We already have chat apps WhatsApp, signal, telegram …” – greatgib
- “TIL that RCS was designed as a fairly decentralized protocol … but it didnt get adoption. So Google stepped in … and now mostly all RCS is centralized on Google's servers.” – sva_

2. Feedback on the messaging app’s UI and functionality (including regressions)
Users praise the visual refresh but point out usability regressions, especially around copying OTP codes and link handling, and express a broader wish for a polished, modern messaging experience.
- “Looks prettier but a shame an obvious regression happened for one of my primary use‑cases: copying one‑time codes. Long pressing on a link selects the entire SMS instead of bringing up a menu for the link.” – gib444
- “It's doubly disappointing because just 4 days ago the project wrote … on using AI for the new Messaging app …” – gib444
- “Messaging can be replaced with one of the hundreds decent messaging apps. Unlike the backup app which is utterly unusable …” – subscribed
- “That was really fast, they only announced it like a day or two ago IIRC? Also: no screenshots of the redesigned interface?!” – LoganDark

3. Calls for screenshots / visual documentation
A recurring request is for screenshots or other visual aids to convey the new interface’s look and feel, reflecting the belief that images are essential for understanding functionality.
- “How about some screenshots?” – cloudie78
- “I constantly see those projects that would benefit from a screenshot in a readme, but for some reason the thought about adding one doesn't even come to the authors' mind …” – qweqwe14
- “I think in many cases the authors value functionality much more then esthetics.” – gbalduzzi
- “In many cases the repository isn't meant to be more than for source code too …” – embedding‑shape
- “A picture is worth a thousand words” – Dig1t


🚀 Project Ideas

Generating project ideas…

OTP Helper – Android Accessibility Service for One‑Tap OTP Copy

Summary

  • Provides an accessibility service that detects 6‑digit one‑time passcodes in incoming SMS and surfaces a copy‑to‑clipboard action (notification or overlay button).
  • Solves the regression where long‑pressing a link selects the whole SMS instead of offering OTP copy, restoring a fast, secure 2FA workflow.

Details

Key Value
Target Audience GrapheneOS and privacy‑focused Android users who rely on SMS for 2FA
Core Feature Real‑time OTP detection with a single‑tap copy action (optional auto‑copy)
Tech Stack Kotlin/Android, Accessibility Service API, regex pattern matching (optional ML Kit for robustness)
Difficulty Medium
Monetization Hobby

Notes

  • Addresses gib444’s frustration: “shame an obvious regression happened for one of my primary use‑cases: copying one‑time codes.”
  • Enables users to keep using the stock GrapheneOS messaging app without sacrificing OTP usability, a pain point repeatedly mentioned in the thread.

SeedVault++ – Reliable Encrypted Full‑System Backup for GrapheneOS

Summary

  • Implements a trustworthy, incremental, client‑encrypted full‑device backup solution with a simple GUI and recovery‑mode restore.
  • Replaces the “crap” Seedvault experience with a robust, auditable tool that lets users back up apps, data, and system settings to local storage or OTG drives.

Details

Key Value
Target Audience GrapheneOS users who flash frequently, need disaster recovery, or distrust current backup options
Core Feature Block‑level incremental backups, end‑to‑end encryption (e.g., libsodium), scheduled jobs, one‑click restore from recovery
Tech Stack Rust core (backup engine, encryption, compression), Kotlin/Android UI, uses restic/borg‑like repository format, optional UI via Jetpack Compose
Difficulty High
Monetization Revenue-ready: One‑time purchase $9.99 (optional support tier)

Notes

  • Directly responds to lollobomb: “long‑awaited full system backup feature… Seedvault is crap, not an option.”
  • Provides the verifiable, encrypted backup that privacy‑conscious GrapheneOS users have been requesting, reducing reliance on Google services.

AutoSnap – CI‑Driven Screenshot Generator for Android Open‑Source Projects

Summary

  • GitHub Action that builds an Android APK, launches key UI flows via Espresso/UI Automator, captures screenshots, and updates the project README with the latest images.
  • Eliminates the manual overhead and tunnel‑vision that causes maintainers to omit screenshots, keeping documentation visually accurate.

Details

Key Value
Target Audience Open‑source Android maintainers and contributors who want up‑to‑date visual docs without manual effort
Core Feature Automated screenshot capture of main activities/dialogs on every PR or scheduled run, with diff‑aware README updates
Tech Stack GitHub Actions, Gradle, Android SDK, Fastlane screengrab or custom UI Automator scripts, Jekyll‑style markdown patching
Difficulty Medium
Monetization Hobby

Notes

  • Reflects repeated calls for screenshots: “A picture is worth a thousand words” and comments about missing screenshots in READMEs (e.g., embedding‑shape, qweqwe14).
  • Gives maintainers an easy way to showcase functionality, addressing the UI/UX concerns raised about the new GrapheneOS Messaging app and other system apps.

Read Later