Native linux? Does axolotl count? If so, it's been there for a while, and keeps being developed and maintained AFAIK... Ubuntu touch delivers a gnu+linux phone binary as well.
this post was submitted on 29 Jun 2021
16 points (100.0% liked)
Linux Phones
6325 readers
1 users here now
Community about running GNU/Linux on phones. Projects like Ubuntu Touch, Plasma Mobile, PostmarketOS, Mobian etc. Either on former Android phones or hardware like the PinePhone.
Related communities:
See also:
Related chats:
founded 5 years ago
MODERATORS
Yes the Ubuntu Touch version was recently updated and seems good? Have not tried it myself as I am not using Signal.
Interesting, reaching version 1.x !
Changelog:
1.0.0 (Mai 28 2021)
From my understanding, axolotl doesn't yet support v3 groups, which is most of them nowadays.
well, it's not v3, it's v2. There's an axolotl issue about that. And that made me aware of 2 other projects, whisperfish, which I'm not that interested on, and flare which does look really promising (though I don't understand why the preference of qt-quick/qml over qt).
So, 2 additional gnu+linux clients you might take a look at... Though none of them supports the new groups v2 yet.
(though I don’t understand why the preference of qt-quick/qml over qt)
Makes mobile support much easier and is generally nicer to work with IMHO.
Perhaps, but there's performance penalty, :( Qt should be ok on mobile AFAIK, though it seems now the trend is c++ disliking. Granted it's harder. On the positive side, at least it's not electron, :)
Let me guess, you "need" a more sophisticated UI toolkit on mobile? ;-p
With Qt Widgets you'll have to go out of your way to make it work nice with touch devices, since it has been created for desktop usage with mouse and keyboard input in mind, while Qt Quick has been made with mobile user interfaces in mind.
I wonder why you're worried about the performance of Qt Quick. It has hardware rendering by default and the layout system is designed with applications in mind, unlike HTML, which tries to retrofit a document markup language into an application markup language. Additionally, QML and JavaScript files can be precompile to native code, if the JIT compilation of QML and JavaScript files would be a performance concern.
QML just sits in this sweet spot of being easy to use for developers while not consuming too much ( Electron-levels) of system resources. Of course, if you abuse QML you can most definitely create slow applications in it, but you could say that about every framework.
+1 for QtQuick/QML. Stuff like NeoChat is really inspiring (even though there's a lot to be done still in mobile).
Ah I wasn't aware of whisperfish and flare.
Thanks for the two web links. They seem pretty related btw.
The company behind Signal is hostile towards third-party clients connecting to their server, so I imagine that puts off people from investing too much work in that.