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, 1:56:48 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

87 sources
I had started peddling Signal to my family members. Then Signal shot themselves in the foot by killing the SMS import functionality. SMS integration was the killer feature of Signal for bringing more people on board and get to a critical mass of users, where uninstalling WhatsApp would be a a viable option. It seems that you can still get the SMS import by first installing an old version that supported it and then upgrading (see [1]). But obviously this is only an option for techies, not moms and pops. [1] https://github.com/signalapp/Signal-Android/issues/8887#issu...
In WhatsApp has removed answer to “how do I choose not to share data with FB”
This thread is full of people suggesting to just switch everyone, including grandma, to Signal/Matrix/Telegram/XMPP. This is naive. First of all, I'm a big fan of Signal and Matrix, but it is hard to overstate how much more polished WhatsApp is in comparison. There's just a lot more friction for grandma. There are also considerably fewer resources behind the alternatives, so things like this [0] happen (tl;dr - it took Signal over seven months to fix a bug in the Android client that would sometimes send messages to the wrong person!!) Second, the problem doesn't end with grandma. It's the network. There are literally billions of people on WhatsApp and there are places where WhatsApp is the default method of communication for everything. Schools and kindergartens use it for announcements and to communicate with parents. Service providers g
Read the rest
ive out a WhatsApp number to contact support. Friends and family are all on WhatsApp in established groups with a long history that everyone wants to keep. Trying to switch everyone over is futile. Not being on WhatsApp isn't an option. It is that big. [0]:https://github.com/signalapp/Signal-Android/issues/10247
In WhatsApp has removed answer to “how do I choose not to share data with FB”
> Telegram has a lot of hacks but HN doesn't throw a fit. It had the attention of HN. They seem to care about both Telegram and Signal's flaws. Just like you highlighting the 'security issues' in Telegram, there is no escape of highlighting Signal's 'security issues' and security researchers will do exactly the same. Once again, there are no exceptions. > Besides, Telegram still isn't e2e by default, doesn't have e2e groups, and has no security audits. I'm not sure why this is in the same category as Signal. I expect better from a 'secure alternative' that claims to be focusing on 'privacy and security' and that also proudly shows its list of security audits. Despite all of that, they introduce their own cryptocurrency coin just to get it listed on an exchange and used in Signal, Similar to Telegram's own cryptocurrency venture which fail
Read the rest
ed. [0] Combine that with the security issues in this post which one of them taking half a year to fix and still using a phone number to login, it is no different to Telegram. They still haven't even fixed this serious security issue either. [1] The worst part of all of this is their prioritisation on addressing these issues and went in favour of creating a cryptocurrency coin just like Telegram, which most likely explains the 7 months to address that security issue. At this point, their claim of upholding privacy and security is already damaged by all of the above. [0] https://www.theverge.com/2018/5/2/17312046/telegram-initial-... [1] https://github.com/signalapp/Signal-Android/issues/10247#iss...
In Signal on Android: Images sent to wrong contacts
If you call it a "whim" if I point out that the latest version of the Signal server is proprietary software most of the time then so be it. Or maybe you are referring to the other commenters who were entitled to expect that the one critical task of a crypto messenger is ensuring the confidentiality of communication, which has been broken by this bug (and at least one similar bug before it, https://github.com/signalapp/Signal-Android/issues/7909 ). You can both be grateful that Signal is free and at the same time call out shenanigans of its owners. Just saying.
In Signal on Android: Images sent to wrong contacts
Signal typically delay releasing the server source code, so the latest version of the server is not open source. In one case it took them almost a year (no public commits between 20 April 2020 and 6 April 2021). https://github.com/signalapp/Signal-Android/issues/11101#iss... Among the official reasons given was staying ahead of spammers. In this instance it was also speculated that the payment function which they were building into the server was to remain secret. https://github.com/signalapp/Signal-Android/issues/11101#iss...
In Signal on Android: Images sent to wrong contacts
Calm down, I only said at worst for Quill, it seems like now I have to question your reading skills. > If all you have on Signal is opt-in feature for payment, and an issue of usernames that's being worked on... Opt in or not, don't think I want cryptocurrencies in my chat app. Look what happened to Keybase after that. Usernames of some kind should have been be there from day one. We don't need any more phone number leaks. Also don't forget that Signal cannot end calls properly and the recipient is still able listen after the call has ended. Very bad. [0] [0] https://github.com/signalapp/Signal-Android/issues/10247#iss...
In Signal on Android: Images sent to wrong contacts
A lot of people are talking about the bug but not the fix. Is anyone else incredibly surprised that the fix was just adding auto_increment to the primary key column for two tables[0][1]? Not having these as auto_increment seems like incredible oversight to me. In what common scenario would you want a setup like that? [0] https://github.com/signalapp/Signal-Android/commit/83086a5a2... [1] https://github.com/signalapp/Signal-Android/commit/b9657208f...
In Signal on Android: Images sent to wrong contacts

Showing the 15 most recent of 87 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.