GrapheneOS Overhauled Default Apps and Secure Clipboard

Original Article ↗ Hacker News Discussion ↗

GrapheneOS is overhauling its aging default Android apps, starting with a fully modernized Messaging client and plans for a new gallery based on a fork of the Apache-licensed ReFra project, while also introducing a “secure clipboard” feature. A major goal is to add standards-based RCS with end‑to‑end encryption (via Messaging Layer Security) so users can have private, interoperable messaging with iOS and Google Messages users without relying on Google’s own app. Commenters debate the value of RCS versus third‑party messengers like Signal, licensing constraints that rule out some popular FOSS apps, and whether investing further in AOSP makes sense as Google tightens control over Android.

RCS, SMS/MMS, and Messaging Ecosystem

  • Many see RCS as a technical upgrade over SMS/MMS: better group chats, higher‑quality media, typing indicators, and (in newer specs) end‑to‑end encryption via MLS.
  • Others argue RCS is inferior to apps like Signal, was carrier‑driven, and now largely controlled by Google, undermining openness.
  • Regional differences are emphasized: in the US, default SMS/RCS/iMessage are dominant and WhatsApp is rare; in much of the rest of the world, WhatsApp and other OTT messengers dominate and RCS is largely irrelevant.
  • Some users report RCS reliability problems and migration pain, leading them to abandon it.
  • There is concern that RCS gives carriers and Google renewed leverage (e.g., monetization, ads), though others stress it’s still far better than plain SMS if implemented with E2EE.

GrapheneOS Position on RCS and Secure Clipboard

  • GrapheneOS wants RCS to provide out‑of‑the‑box E2EE with mainstream Android and iOS users without forcing them onto third‑party apps.
  • They frame RCS as a necessary evolution of SMS/MMS rather than an endorsement of it over Signal/other messengers.
  • Some commenters want GrapheneOS to actively promote an open, privacy‑focused messenger by bundling it; GrapheneOS prefers to stay neutral and only handle carrier‑based messaging.
  • Secure clipboard is mentioned as a separate new feature, with its own announcement thread.

Overhaul of Default Apps (Messaging, Gallery, Keyboard)

  • The stock AOSP apps, especially Messaging and Gallery, are widely viewed as outdated and clunky.
  • GrapheneOS has fully rewritten the Messaging UI with modern Android UI tech, focusing first on parity and maintainability, with RCS support planned later.
  • They intend to replace AOSP Gallery, likely by forking an Apache‑licensed project (ReFra) and stripping or reshaping integrations.
  • Multiple alternative keyboards are discussed; users praise some third‑party options, but licensing and usability constraints limit what GrapheneOS can bundle.

Licensing Constraints

  • GrapheneOS wants its core OS to remain no more restrictive than AOSP (GPLv2 + permissive); GPLv3 and “source‑available” licenses (e.g., FUTO keyboard) are considered incompatible for preinstalled apps.
  • Some argue GPLv3 aggregation would be legally fine; GrapheneOS reiterates it is a deliberate policy choice, not a legal impossibility.

Android/AOSP Dependence and Future

  • Debate over Google’s tightening control of Android and whether a future hard fork is viable.
  • Many note app ecosystem lock‑in: any non‑Android mobile OS struggles due to lack of mainstream apps.
  • GrapheneOS is seen as pragmatically building on AOSP for security and compatibility while acknowledging long‑term uncertainty.

Use of AI in Development

  • GrapheneOS stresses they do not “vibe code” with LLMs.
  • They use models mainly for code review and generating tests, claiming higher code quality and more issues found, while keeping strict human standards.