Add note about maintenance mode #996
Conversation
|
Any more detailed description of what the "new solution" will look like / be? Just curious ;-) |
|
We hinted a tiny bit in #991 but that's all we want to say at the moment. 🙂 |
|
Now being for months in homeoffice, I am even more curious: is there a new web client or even a desktop app available for Threema? The normal web client is - hmmm - a bit cumbersome ... ;-) Some beta already available? |
|
Not yet. But in the meantime more information was published regarding the new approach we're working on: https://threema.ch/en/blog/posts/md-architectural-overview There will be a web/desktop client which will work as a fully standalone Threema client, synchronized with your mobile device. Planned for 2021 (but probably not early 2021). |
|
ah, okay. Thanks for the info 👍 |
What exactly do you mean with "web/desktop client"? Will it still be possible to use Threema in the browser? Or just a standalone desktop-app like Signal has? I (personally) really hope there will be a web-based solution, too. Having to run multiple desktop applications (one for each messenger) is just making the inconvenience of having contacts split over different (mobile) apps even greater. Using Rambox/Hamsket, Ferdi or even just a dedicated browser window for all chats is so much more efficient both time- and screenspace-wise. Don't get me wrong, starting a daemon process in the background for the mediator server is perfectly fine (as long as you can connect to it via a local web frontend), but being forced to open a separate window/desktop app for every service doesn't really make communicating easier than before. |
|
|
any news already re a new client? waiting eagerly ;) |
|
Working eagerly. 😉 |
|
I just installed Threema desktop. Is that the new solution? It looks like electron with Threema Web and still no dark theme. Or am I missing something? |
|
Sorry, just noticed now there's a "threema desktop 2.0" coming, I assume this is the "new solution"... |
It's almost exactly that and it's not the new solution. |
|
Just checking in to see if there's any more news about the new client. I still see the original announcements/document s from Dec. 2020 and the latest screenshot/news I can find are from 30.12.2021 on Twitter. The current desktop app is OK. It ends the session a lot, so it's not useful for getting updates for more than 10 or 15 minutes. That makes it difficult to convince people who don't like doing everything on their phones to switch from Signal/etc. A sign of life here would be very much appreciated. |
I would disagree with that. It works well with all Android smartphones that don't have dreadfully patched OSes killing stuff randomly in the background, e.g. Samsung. But this is where we are today - unfortunately, people tend to not care about who is responsible and blame everything on the apps. But that's just my frustration and it's likely besides your point.
We're working on it like crazy. I'm not sure what else I can say? |
|
Thanks for the quick reply! "Working on it like crazy" is enough of a sign of life for me, TBH. I just noticed that it had been six months since I'd heard anything (screenshot/tweet above) and that the initial announcement of the new architecture had been made 2.5 years ago. As for my experience with the current desktop, I regularly see the open desktop app, with a conversation selected. I can even write a message, but when I submit, it shows the "Reload Session" button and throws away the comment. I've gotten used to just clicking a different conversation first to see whether I'm still "logged in". That way I don't lose any message text. It's just not ideal. Signal is much more comfortable as a desktop client (although their nearly daily updates are also not super-reassuring). I have an old iPhone 6S (although I doubt that plays into it). Maybe I'm the weirdo for using a desktop/web version, but it's so much more comfortable to use a real keyboard and to be able to copy/paste from a real browser. I know a lot of people are exclusively on their phone, though. Hey, I'm happy to hear you're working on it. I also understand if you're going with the old Id Software roadmap: "when it's done." Thanks again for the quick response. |
1 1/2 years since the announcement. But obviously there was internal work before, so your number is actually close. 🙂
The iPhone experience of Threema Web is indeed rough. There's no way of denying that. What you're describing does sound like a bug though but I know that there's a couple of fixes currently in the beta rolling out soon.
Absolutely not weird - I don't like typing on smartphones either and (obviously) use Threema Web all day.
Thanks! That being said, the whole Threema team would like to have released Desktop 2.0 already. Besides technical challenges on the Desktop 2.0 code base itself, let me name a few other reasons why it takes so long: Multi-Device protocols are very complex if one wants to prevent desyncs and conflicts. Another challenge is to update the existing code of the apps so that they harmonize with each other. This is vastly more difficult than writing another Threema client as they exist today. And I think it's fair to admit that, even though we were prepared, the magnitude of it still took us by surprise. |
|
@lgrahl |
|
Just checking in for any updates on the new desktop version. The current version has gotten much worse now, with iOS forcing the phone to be on, open, and showing Threema in order to use the desktop. I know that's not Threema's fault, but the reality is that the existing desktop client has been significantly downgraded, UX-wise. I'm hoping to be able to jump to at least a beta of the new multi-device desktop version soon. |
|
There will be a tech preview that allows iOS users to test the upcoming desktop app before the end of this year. Participation for iOS users will be available through the regular iOS beta program. |
|
Hi, Any news on that?:
Was thinking of a Threema account but will wait until we have good news on Multi-Device protocols also. Telegram anonymous number will do the job for now for this very corner case (daughter without phone right now). |
|
Hi @matbgn, the preview is already available since early December 🙂 https://threema.ch/en/blog/posts/ios-test-multi-device Work to add more features and improvements is still ongoing. The changelog can be found at the bottom of the download page. To not miss out on such announcements in the future, make sure to subscribe to the Threema Channel! |
|
Can we expect an Tech Preview for android users in the near future too? |
|
@Kasi07 not in the near future unfortunately, since our number 1 priority is getting a feature-complete Threema 2.0 for desktop out to all iOS users that must currently live with massive limitations when using Threema Web/Desktop. However, the good thing is that all work that goes in to the Desktop application will also benefit all Android users in the future (since they will have a feature-complete desktop application from the start). The Android integration for the multi-device protocol is already being worked on, but it will still take a while until it's ready. |
If I may ask, what could "a while" mean: weeks, months, half a year, a year, years? |
|
We made predictions before, and they were sometimes way off, so we prefer not to do that anymore 🙂 I use Android myself, and I definitely want to be able to use Threema Desktop with my Threema apps as soon as possible, too. |
|
I wonder how many people you've already lost over this clunky piece of software. Basically every other messenger platform is able to pull off a decent desktop experience except Threema. Most of them are free as well. It's been three years now since anything worthwhile has happened in this space, and I for one gave up on it completely a few months ago. Which in turn pushed the mobile app into oblivion as well. |
|
@maryisdead you can track the current development progress of Threema Desktop 2.0 at https://threema.ch/en/download-md. The changelog can be found at the bottom of the page. |
|
I'm currently looking into bridging Threema to Matrix via the web ARP, similar to what mautrix-whatsapp is doing. Is it worth holding off until you release this? |
Interesting idea. Be aware that the ARP is designed for trusted devices of the user, so security might be an issue. Moreover, once Multi-Device has been implemented in Threema for all platforms, it is planned to remove the Threema Web code and therefore retire the ARP. |
|
That's what I thought - no use putting in the work now if the ARP is going to be retired. Thanks for the heads up! Will there be a different API in its place that would make this possible? I am aware of the security issue - since bridges terminate the end-to-end encryption of the bridged service and re-encrypt the content for the Matrix side, they are conceptually required to be trusted. That's why Matrix based services have the option of self-hosting the bridges (which is what I intend to do). |
|
If you count the multi-device protocol as an API, then yes. That being said, the multi-device protocol will be way more challenging than the ARP. |
|
Sounds like a way more sensible solution for the purpose though, if you could treat the bridge as its own independent device. Very exciting, can't wait to learn more! |
|
So here we are in mid 2024 now. It's been 4 years. I realise things take time and Threema isn't exactly a massive company. Still 4 years later and there's really been zero word on this still. No "product demo" or "nightly" or anything I can see that we could test. Maybe that's a good thing as far as security flaws are concerned but could anyone disagree that maybe now it's time for a knock at the door? How is the status of this going? Threema web is extremely basic at this point. One of my most used apps on my Desktop is Whatsapp and Signal. I would like to replace both with Threema. In fact, the reason I am here is because when sending voice messages. I simply cannot play them in Threema web/desktop. I click play and nothing happens. This is when I am connected via Bluetooth to my PC. Neither the web browser or desktop app work.
Is this "new" architecture still coming? |
|
@825i Threema 2.0 for Desktop is available since December 2022 (was a preview, is now a beta). Unfortunately not yet in combination with an Android device but we're getting there. |
is there any way to get a feel if android support for desktop 2.0 is taking more like 2 more months or 2 more years or 20 more years? its been a while and the changelogs of 2024 do not mention the word "android" a single time; i would love to be able to have calls and conferences on threema desktop even as a what feels like "second class" non iOS user I dont want to bully you with this post, but there is no explanation other than "its complicated, we´re working on it trust us bro" and it is starting to become frustrating. I would prefer getting access to a non feature complete version of the desktop app 2.0 and all its already nice features (other messengers have had for years "but of course they can do it as they dont particularly care for security nor privacy" ...) instead of waiting for another 4 years for the perfect thing to drop. This is all I could find on the website https://threema.ch/en/blog/posts/md-architectural-overview -> Nov, 2020 "We have the solution, the details need to be worked out" https://threema.ch/en/blog/posts/threema-for-desktop -> Oct, 2021 "Implementation is in full swing but more intense than we imagined, well have a preview/beta by the end of the year" https://threema.ch/en/blog/posts/ios-test-multi-device -> Dec, 2021 "Heres the preview (btw only iOS atm; android support planned)" https://threema.ch/en/blog/posts/ios-new-desktop-app -> Sept, 2023 "Heres the Beta🥳🥳🥳 (btw only iOS atm; android support underway)" https://threema.ch/en/blog/posts/data-security-of-threema-for-desktop -> Jul, 2024 "Our Desktop App is best/safest 🥳🥳🥳(btw only available to iOS)" https://threema.ch/en/blog/posts/desktop-group-calls -> Jul, 2024 "Groupcalls for Desktop are here 🥳🥳🥳 (btw atm only iOS guys, android support development underway)" https://threema.ch/en/faq/md_overview -> "its only for iOS, Android support is underway" many of the blogpost then reference the faq for further information, which it provides but only very limited and not on the android issue. . https://threema.ch/en/blog/posts/swiss-german -> nice to see translating the app to a particular dialect of swiss german is a priority (although I do have the mental capacity to see that it hopefully didnt cost android support development hours) |
|
I can assure you that finishing the integration into the Android app is priority 1 of the Android development team. And it should be obvious that adding new translations don't make the Android developers any slower. The development of the desktop app is happening in parallel by a different team. Which has the advantage that - once the Multi-Device integration into the Android app is here - you will be able to use all its features from the start. |
Threema Web is in maintenance mode while we are working on a new solution that should resolve some of the long-standing issues we were having with Threema Web. We will still do regular maintenance and fix critical bugs, but for now there will be no major new features.