Conversation

It's also completely possible that they'll do things like migrating their code to Kotlin similar to how they started replacing Objective-C with Swift in their iOS app. It can definitely work long-term, but it depends on keeping up with everything that ends up changing in Signal.
1
1
Replying to and
I'm wary of building anything on their code or forking anything to make changes because of their hostility towards alternate clients using their servers and their lack of need to preserve any backwards compatibility due to forcing upgrades, which is an overall positive thing.
1
2
There's the option of running the Android app in the official KVM-based Android emulator but that only acts as the main client rather than a secondary client like the desktop app. It honestly probably uses less memory than Signal Desktop, especially after being open a while.
1
Replying to and
I think KDE Connect can bridge the notifications including replying to them from the desktop but I'm not sure if that requires using KDE. I just feel like trying to use an unofficially supported client is a recipe for ending up needing to do a fair bit of work to keep it working.
2
Replying to and
I use KDE Connect already, but the Android app -also- sucks. Sometimes I get a message on the Desktop app and five minutes later long after I read it the Android one finally sends me a notification.
1
Replying to and
I'm used to the non-GCM push implementation on devices without Google Play which works essentially the same way as the desktop app. GCM is efficient but it's not particularly reliable and often has delays. The efficiency is mostly from apps reusing the same connection anyway.
3
1