HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
element-hq
element-x-ios
Swift2022–2026
element-hq / element-x-ios

element-x-ios

Next generation Matrix client for iOS built with SwiftUI on top of matrix-rust-sdk.

7Distinct people
18Mentions
0Explicit recommenders
973GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Next generation Matrix client for iOS built with SwiftUI on top of matrix-rust-sdk.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:02:05 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 year18 dated mentions

Observed mentions: 2022-10-27 11:20:57 UTC to 2026-07-11 11:43:30 UTC.

02462022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 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
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC404
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC606
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC606
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC110

What Hacker News says

6 sources
> honestly, without annotated screenshots filed in github.com/element-hq/element-x-ios/issues to highlight precisely what the problem is (ideally comparing with an equivalent app which you feel gets it correct) i’m not sure we’re going to be able to help you. I mean, I'm not asking you to help me, I was just curious whether there was any more resources dedicated to the UI/UX of that particular view. If the answer is "no, and we feel the view is fine", then just say that. I might not agree with your choices but it's not going to stop me using the app. ;P I'm unlikely to stop and annotate a bunch of screenshots and put them on GitHub as I've other things to do with my time. The older I get, the more protective I am of my free time... as much as it sucks from an OSS perspective. > the green box sounds like an accessibility helper feature of
Read the rest
some kind which has got confused? You mean in Element X itself? I have no accessibility features enabled on my devices, so I doubt it's an OS-level control in the way.
In We have lift-off Element X, Call and Server Suite are ready
honestly, without annotated screenshots filed in github.com/element-hq/element-x-ios/issues to highlight precisely what the problem is (ideally comparing with an equivalent app which you feel gets it correct) i’m not sure we’re going to be able to help you. the green box sounds like an accessibility helper feature of some kind which has got confused?
In We have lift-off Element X, Call and Server Suite are ready
> the typical reaction from an Element dev is “it works fine for me, make a PR or something”, This is false. We check issues which people file and try to reproduce them, and we certainly don't ask randoms to contribute PRs to fix stuff - we'd much much rather fix them ourselves. Meanwhile, you can see the issue stats at github.com/element-hq/element-x-ios/issues and github.com/element-hq/element-x-android/issues - it's not like we're ignoring or failing to close issues.
In We have lift-off Element X, Call and Server Suite are ready
Matrix itself is a big messy thing, much like the Web - this is both its power and a potential weakness. Element X is indeed a fancy new client - but it hasn't hit a 1.0 yet. Think of it a lot like Firefox was pre-1.0; it's unrecognisably faster and better than the previous generation... but not all features are there yet. Meanwhile, there are loads of entirely unrelated independent excellent clients out there too; it's not just about Element v Element X. > But I wasn't able to set up the encryption with my recovery key, there was only the online validation which I couldn't use because I was on the go and didn't have access to my desktop. This bug is an accidental thinko however: it's placeholder UI which is about to be replaced by implementing login-via-scanning-QR-code (which is almost there), but obviously that also needs the ability
Read the rest
to enter recovery keys too. Eitherway, it's being fixed: https://github.com/element-hq/element-x-ios/issues/2424 EDIT: looks like a fix landed on Friday: https://github.com/element-hq/element-x-ios/pull/2471 > also seems to still lack TOFU for my private server Yup, sorry, TOFU for TLS isn't implemented yet in EX. > The same with the homeservers, there's synapse and dendrite is supposed to take over at some point but that point is forever far in the future. And then there's conduit, so which one is it? Synapse is a stable server where the core team is putting its effort currently. Dendrite is a 2nd gen server from the core team, but is beta and a) ended up being focused on P2P and embedded homeservers and experimental MSCs, b) is starved of resource atm due to funding pressure (c.f. https://www.youtube.com/watch?v=s5BrVVf0B1I&t=316s). Conduit is an independent server implementation in Rust, which is promising but beta. It's like asking whether you should use Apache httpd or beta versions of nginx or lighttpd in the early days of the Web. > The strategy doesn't really feel well thought out in that sense. The strategy at Element (which employs most of the Matrix core team) is pretty clear right now: 1. Improve Synapse as the most mature and stable server implementation (and package it in Element Server Suite for those needing an enterprise Matrix distro: https://element.io/server-suite) 2. Finish implementing sufficient features in Element X that it can replace the old classic Element mobile apps asap - converging on a single Rust codebase, so that bugs & audits & new features can all land in one place. 3. Keep building Element Web/Desktop and Element Call. ...and that's it. If it seems confusing, that's either because we're in the middle of the Element -> Element X shuffle... or because the nature of Matrix is that there's loads of other independent implementations running around too. But that's what makes it fun, too :)
In Signal v7.0.0 with phone number privacy

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.