HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
signalapp
Signal-Android
Kotlin2011–2026
signalapp / Signal-Android

Signal-Android

A private messenger for Android.

280Distinct people
372Mentions
5Explicit recommenders
29.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A private messenger for Android.

GitHub

Where it is used

  • Molly — Molly uses the signalapp/signal-android codebase as an independent fork to deliver a variant of the Signal Android app with added features. It ships as its own app built from the Signal Android project. Source

What people are saying

I never hated on Signal, on the contrary I recommend it too many people but I can say that the energy consumption on Android is in many cases abysmal for multiple years now and…

johschmitz used a recommendation phrase. 5 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 3:16:21 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year372 dated mentions

Observed mentions: 2011-12-21 12:48:31 UTC to 2026-10-12 11:10:46 UTC.

0204060802011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20112012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 12 mentions; 0 submissions, 12 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 23 mentions; 0 submissions, 23 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 26 mentions; 1 submissions, 25 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 46 mentions; 1 submissions, 45 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 22 mentions; 2 submissions, 20 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 24 mentions; 4 submissions, 20 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 25 mentions; 1 submissions, 24 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 87 mentions; 12 submissions, 75 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 30 mentions; 2 submissions, 28 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 13 mentions; 0 submissions, 13 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 16 mentions; 2 submissions, 14 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 23 mentions; 1 submissions, 22 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC110
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC413
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC12012
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC23023
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC26125
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC46145
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC22220
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC24420
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC1019
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC25124
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC871275
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC30228
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC13013
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC16214
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC23122
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC10010

What Hacker News says

23 sources
> Surprised how many people don't seem to know about it. There are a few reasons for that. 1. The link to APK cannot be found on the official site[0], so it needs to be looked up in a search engine. 2. Even when downloading from the site, they try to scare you away with a warning [1]. The reason for warning could be avoided by hosting their own F-droid repo, but they refused it, claiming you can download APK and not listening to reason[2]. Though for people using F-droid can still get Signal through the Guardian repository [3] Thing about the signal APK and the Guardian one is that, it still have the so called "crap" in the final APK, it just runs a background service when required google services are not detected, causing battery drain for many[4]. The drain could also be avoided by supporting UnifiedPush (it can fall back to FCM when it
Read the rest
In Molly: An Improved Signal App
> It sounds good in theory but signal updates are beyond excessive Those are two different arguments. Updating too frequently is not equivalent to "doesn't need to be updated." I can agree that they update a bit too frequently but that's nowhere near the argument about never updating. A program cannot be secure if it does not update. Full stop. > Most of the time there is zero explanation for the update There's always a changelog. If you, unlike most people, are interested it is all open source https://github.com/signalapp https://github.com/signalapp/libsignal/releases https://github.com/signalapp/Signal-Android/releases https://github.com/signalapp/Signal-iOS/releases https://github.com/signalapp/Signal-Desktop/releases I would suggest looking at the actual commits and not just the release notes. Libsignal usually has mor
Read the rest
e info about the security > legitimately can't think of another app or program that updates more frequently Probably because they do so silently.
In Molly: An Improved Signal App
"fdroid repos" have little to do with what people consider F-Droid, they can host any whatsoever binary. In fact, that's not a build by the Guardian Project, but (when I tried) a redistribution of Signal's https://github.com/signalapp/Signal-Android/releases builds. I'm not sure why they're doing it; anyhow, I'd at least avoid doing the initial installation through that repo, you're trusting an additional party for no gain that I could think of (updates are ok because the signature needs to match the one of the installed version).
In Molly: An Improved Signal App
Hi! I don't know if we'll have anything super official, but the code is obviously all open source, and the backup file is just a stream of protobufs[1], so it shouldn't be too bad to make a tool. I know have some rough CLI tools sitting around -- I'll see if there's anything we want to clean up and release publicly when the local backup portion of this launches. Also, as someone else noted, the format is indeed incremental. So while we'll still do the thing where we keep the last two backups on disk, because those two backups will share almost all the same media files, the size on disk will be much much smaller. As someone with a 50 GB backup file, this was very much a goal for me :) [1] https://github.com/signalapp/Signal-Android/blob/main/app/sr...
In Signal Secure Backups
Apple is very explicitly and deliberately building their systems to forcibly collect massive amounts of user data that they can and do provide to the federal government. While it is true that close to all companies will comply with lawful orders (but not EVERY company, FWIW: Lavabit famously shut down instead of handing over SSL keys to feds), it is possible to design systems in such a way as to protect FAR more user data privacy than Apple does. Case in point: review the contents of Signal's subpoena response a few years ago: - https://signal.org/bigbrother/cd-california-grand-jury/ This isn't a sham privacy claim like the kind made by Apple that requires you to trust the provider, either. Signal's clients are famously open source - something Apple does not do for pretty much any part of iOS or Mac OS: - https://github.com/signalapp/Sign
Read the rest
al-Android - https://github.com/signalapp/Signal-iOS - https://github.com/signalapp/Signal-Desktop Additionally, most of the Signal server's source code (nix the anti-spam components) is open source, as well as the libsignal library used across the clients and server alike: - https://github.com/signalapp/Signal-Desktop - https://github.com/signalapp/libsignal Apple could be this transparent if they wanted to. They choose not to be, because the truth is, they do not actually care about user privacy, they are constantly collecting massive amounts of telemetry, user data, and user metadata from every single device they make, and they have been proven to share this data extensively with the federal government via the Snowden leaks, even in spite of the few actions they take publicly to maintain the marketing illusion of being a company that cares about user privacy, such as in the wake of the San Bernardino shooting.
In Apple pulls iPhone torrent app from AltStore PAL in Europe
> Contrast that with e.g. matrix.org (where the majority of Matrix users are) This effectively confirms that federation is important, i.e., you shouldn't use the same server as everyone else, for your security. > Due to its (afaik) unrivaled privacy-preserving architecture https://news.ycombinator.com/item?id=29888228 https://news.ycombinator.com/item?id=39445976 https://github.com/signalapp/Signal-Android/issues/13842 https://news.ycombinator.com/item?id=42788647
In The future is not self-hosted
> Your links are a bunch of user comments? They themselves contain the actual links and also relevant discussions. One more link: https://github.com/signalapp/Signal-Android/issues/13842 > The push notification payloads don't contain message/sender data. The other metadata may be important too. > Signal also runs fine without Google services, which avoids any potential problem entirely. Not everybody is able to avoid Google services on their phone. I can't run it on a desktop (or GNU/Linux phone) without a connection to an Android phone.
In Telegram, the FSB, and the Man in the Middle

Showing the 15 most recent of 23 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.