> In our Linux test it opens in under a second and uses about 200 MB of idle RAM
Is it just me or does anyone else feel that 200 MB is a lot for a native chat app written in Rust, that's essentially a remote interface for the WhatsApp on your phone?
I remember back in the day, apps like Miranda IM (and early versions of Trillian) used only digits of RAM, even when you had multiple plugins talking several protocols at the same time, whilst having a ton of advanced features not found in WhatsApp. Yes I get that times have changed and software has become bloated etc, but 200 MB still feels a bit too much.
> Is it just me or does anyone else feel that 200 MB is a lot for a native chat app written in Rust, that's essentially a remote interface for the WhatsApp on your phone?
> I remember back in the day, apps like Miranda IM (and early versions of Trillian) used only digits of RAM, even when you had multiple plugins talking several protocols at the same time
I think what's happening in the second one is that because you're using the native OS toolkits a bunch of stuff is shared, whereas with these "self-contained" "native"-y apps you end up having to load up the whole world and aren't sharing things with everything else
I'd love to be proven wrong but I feel like if you use e.g. Qt you're gonna have to hold onto a bunch of stuff that you wouldn't if you were "just" using OS-native stuff (though maybe that gets shared if you're using the exact same version? Is there something that can be done in this space?)
As an additional data point, I recently vibed an egui wrapper around a library I wrote for mod management for a game, and testing it out now, it idles at 92 MB. This implies to me that at least half of the overhead is probably not from the gui framework, but I also don't know how much effort they spent trying to optimize it; I didn't try to optimize my vibed GUI app at all, but I did hand-write the library that it uses for file management, state tracking, etc., and I tend to go out of my way to try to avoid unnecessary allocation in my Rust code. I don't know how much of the memory usage is essentially required overhead or from other dependencies for non-GUI parts of the app, but my instinct is that there's probably a bit of optimization that can be done. I don't think it's crazy for them not to have spent the effort on trying to do that yet though (or potentially even at all, if it's efficient enough for their own personal use).
I just checked with the native WhatsApp client on Windows 11:
650 MB of RAM as it is running, across all its processes. Thus, taking ≈⅓ of RAM is nothing to brag about for a reimplementation that focuses on being lean and fast.
Also, "opens in under a second" – back in the days when SSDs where new, programs opened instantaneously (<60 ms)!
Lastly, I still have to be convinced that Rust is a good choice for GUI programs, considering their messy mutable state and ownership.
Matrix bridges for sup, signal and the rest are good enough to never use the web client anyway. You can also skip the part where you need to have it installed on the phone by running waydroid (if you can figure out how to scan qr codes with it).
dont get me wrong, I like the extra performance, but every single alternative whatsapp client has the same issue where it's missing enough core features that you end up needing to go to the browser version often enough to be a nuisance and I end up just using the browser instead (which I hate, I really really would prefer a performant client instead!)
$ cat $(which whatsapp)
#!/bin/dash
# A kiosk is full-screen by design. You need to go to about:config and toggle
# full-screen-api.ignore-widgets to true to prevent our window manager from
# creating an actual full-screen window.
# Additionally, you need to set the name to "kiosk" which will set the app id
# under sway to "kiosk" so that in sway you can disable full-screen on
# startup.
firefox --name kiosk -P whatsapp --kiosk https://web.whatsapp.com/
Egui is pretty bad idea. It uses "immediate mode" rendering which means whole window is redrawn on every mouse move. I ran PhotoCraft (built in Rust + egui) in a VM wihout a GPU and the UI felt like it was running on 3 fps. If you use egui, try running it without a GPU before releasing.
Egui is definitely not what you want to use on a 4K screen. It is only good for tiny screens of embedded devices.
Why there is no reactive UI that tracks all dependencies and redraws only what needs to be redrawn? (not React, it also re-calculates (but not redraws) everything on every change).
Also why does it visually look like bad version of Telegram? And Telegram can run without a phone present.
> Why there is no reactive UI that tracks all dependencies and redraws only what needs to be redrawn?
There's plenty of them. Slint, Floem, iced, Vizia, fltk etc. Slint and fltk in particular also exhibit excellent performance and very little resource usage even without a GPU.
I disagree. First, not every GPU supports Vulkan and other modern standards, and not every GPU even supports executing code. Drivers are often buggy/unsupported. Even if there is a GPU, compiling shaders takes time and CPU must be used in the meantime.
Finally, for app to have access to GPU, it must run on a host unrestricted. Why would you take somebody's code from Internet and run it unrestricted, violating the principle of minimal pivileges? That does not sound smart, especially if you have a crypto wallet on the same computer. Those who do not use VM or sandboxes will sooner or later learn this.
> Did you measure anything in a real setup?
VM is a real setup. Why would I run third-party apps without a sandbox?
Also, today we have an advanced AI that is capable of solving science problems. Should not be difficult to build a GUI that works fast without graphic acceleration, right?
Finally: the modern DDR4 DRAM has approximately 40-50 Gb/s bandwidth. Updating 4K screen at 120 Hz requires 3840 × 2160 × 4 (actually should be 3) × 120 ≈ 4 Gb/s. No problem at all.
This is an app that connects to your phone and sends messages via the app. I don't think it's that crazy to decide that running on a VM or remote desktop is out of scope.
It doesn't connect to your phone, it just authenticates via the app. I deal with a company where people use thin clients that run WhatsApp on the remote desktop. It's not an unusual case.
Interesting, I apparently skimmed the "Link to your phone" section too quickly (and I guess have a different sense of what that phrase implies than the author of that README, since a "link" that no longer requires the other end to exist anymore doesn't really seem like a link at all).
it's an incredible waste of resources, especially at high resolutions, to redraw a Gui application like you would a videogame at 60 FPS. These immediate mode UI frameworks were made in particular for that case, to be embedded in real time software, not for a UI where the state is idle or changes only occasionally.
Redrawing the whole thing consumes resources. That's power and resources not available to other tasks. There is value in being clever with what you draw.
Yes but it comes at the trade off persistent memory usage. It isn’t just free, and depending on the application in question that may be a lot better trade to make if, say, the app runs in the background or is rarely interacted with.
I vibed some code using ImGui and it had this problem. I made it so that it only redraws when data changes with a fixed refresh rate and it went away. So it's not a permanent state of affairs.
To use memoization you must use immutable structures (otherwise React is unable to detect changes) which are a pain to use and are slow if not designed properly. Do not believe me, try designing for example an algorithm that accepts a huge immutable sorted list with keys, a large sorted list of bulk deletes/inserts and produces a new sorted list with minimum operations. I made 2 or 3 prototypes and they still are not good and not even working properly.
In my book, a good UI framework simply attaches to a mutable model made of arbitrary objects, detect changes and displays it with minimum number of operations. Doesn't require to use any proxies or immutable data or store data in components. Shouldn't be difficult. Why nobody made it, I do not understand.
In my head it's retained mode + the diffing layer, which sounds the same but if you try to write an "immediate-mode" API (say, using hooks) in React you'll find yourself churning a lot.
At least unless you use the magic React compiler that memo-izes everything correctly.
> Why there is no reactive UI that tracks all dependencies and redraws only what needs to be redrawn?
Nowadays the focus seems to be on video game-style interfaces that redraw every frame. The justification for this is typically that computers are so fast they can now come up with the entire interface every frame, so why not take advantage of that and forget all this retained-mode complexity?
They don't realize that this is a classic case of the developer's machine fallacy, where the developer has a machine so vastly more powerful than any of their users' that they produce a terrible experience for said users. This is also why games these days typically require upscaling even on 5090, because developers usually have that or something even more powerful and they think the bleeding edge is pushing even THAT machine to its knees.
Developers should be testing their software on the most entry-level, bottom of the barrel Chromebooks from 2015, running the heaviest and most bloated operating system they can think of. If people still optimized their software for that, then maybe computers would still feel almost as fast as the Apple II from 1977.
The GPU will re-render everything anyway. What you can at most optimize is the upload of data to the GPU (i.e. upload only what has changed).
Also consider that if your UI framework supports z-level, opacity and other features like that then determining what has changed for rendering is much more complex than just determining what UI elements have changed.
That's actually a very good point, I haven't seen any care for power consumption from software developers in many many years. The only people who seem to still care about it are hardware developers like Valve and Apple. I admit I never thought about it myself either.
I would figure that doing less work generally requires less power, but some developers are crazy and act like they own the whole CPU, generate tons of heat, stress out the cooling system etc. with multithreaded bullshit that did NOT need to be multithreaded.
Some multithreaded workloads will use the full logical processor count to pin every core and that can really suck on low-end systems. I think aside from balancing multithreading overhead, this is one of the reasons why some more advanced software (such as 7-Zip) lets you select the number of threads to use for a workload, even if you already know and accept that it'll be expensive until it's completed.
Lots of multithreading things I come across as a developer have a default of something like 4 threads, or only use a certain fraction of logical cores up to a certain maximum, etc. because it's generally more polite not to always pin every core.
What purpose would that serve? You have the source code. In the old days we’d just share tarballs. No provenance. It’s fine. You have the unit of legible modifiability.
There have definitely been times when I've cloned repos that were vibed, pointed my own agent at it, and then hacked up whatever changes I've wanted. I don't think there's been a single time that a lack of prompts has caused any issues, but there have been at least a few times where stuff like AGENTS.md checked into the repo has caused hiccups from them encoding stuff that conflicts with how I want things done.
Also, I looked at how dates are written in a screenshot and thought that "2 days ago" would be so much better than "Tuesday". Because you do not have to compute in your head how many days ago Tuesday was.
Sounds reasonable, but IME apps that use relative timestamps switch to absolute time past certain threshold, and then I end up with two adjacent entries "14:38” and "15 minutes ago" and scratching my head.
For an easy-to-read chat list, I chose in a recent tui application to adapt to the age of the message and write only the hour for today's messages, "Yesterday" for yesterday's messages, the week day for 2 to 6 days messages (so this couldn't be ambiguous), month+day for previous messages, year+month+day for last year+ ones. Works pretty well!
I hate relative timestamps, I find it much easier to remember specific week days, so I very much prefer this style so I don't have to compute in my head which day of the week I got the text.
Anyway, I tried this application and it seems to mix different styles depending on how long ago you got the text: "yesterday", "Friday", "18 Oct 2026".
That's the annoying thing with WhatsApp, Slack, Discord, etc. Let's say I've got a personal client (that I'm definitely not using...) which works so much better than the official one. I cannot distribute it or use it according to their rules. It's forced enshitification, even though we have better options.
On the good side though - if you're replicating the official behaviour close enough... maybe nobody will know. But then you have to make sure everything, including key sort order, and JA4 of requests matches. And that's tough...
You don't have to follow their rules but if you don't then you need a backup plan in case they ban you. You need that anyway since people get banned at random, but you especially need it if you're intentionally breaking the rules.
It’s really a shame that all of these unofficial clients are like this. APIs are APIs, if they’re on the public internet why can’t anybody call them? If there’s potential for abuse then that should be secured server side anyway, since needing a unofficial client isn’t going to stop hackers
I think this doesn't apply to European users, as WhatsApp announced around one year ago that under Digital Markets Act they were required to allow interoperability with third party providers [0].
I actually wish they'd delete the warning so then anyone who gets banned from WhatsApp for using an unofficial client would have a more legit cause of action against WhatsApp. Meta wouldn't be able to defend themselves with "well you were warned" if you weren't warned.
Eventually the unofficial client gets "fingerprinted" and its over. Its easy to remove the suspension, though. I vaguely remember it was through email.
Eh, there's no humans any longer IIRC. It's all down to whether their support AI blesses you or not.
I got banned for trying to move my chats from Android to iOS using the app rather than the special tool I didn't know you were supposed to use. I was lucky I eventually got unlocked.
I want a decent WhatsApp client that doesn't crash constantly and where you can search properly, but it's not worth the risk of getting banned again.
> In our Linux test it opens in under a second and uses about 200 MB of idle RAM
Is it just me or does anyone else feel that 200 MB is a lot for a native chat app written in Rust, that's essentially a remote interface for the WhatsApp on your phone?
I remember back in the day, apps like Miranda IM (and early versions of Trillian) used only digits of RAM, even when you had multiple plugins talking several protocols at the same time, whilst having a ton of advanced features not found in WhatsApp. Yes I get that times have changed and software has become bloated etc, but 200 MB still feels a bit too much.
Almost all of those 200MB will be system libraries for rendering and GPU buffers.
> Is it just me or does anyone else feel that 200 MB is a lot for a native chat app written in Rust, that's essentially a remote interface for the WhatsApp on your phone?
> I remember back in the day, apps like Miranda IM (and early versions of Trillian) used only digits of RAM, even when you had multiple plugins talking several protocols at the same time
I think what's happening in the second one is that because you're using the native OS toolkits a bunch of stuff is shared, whereas with these "self-contained" "native"-y apps you end up having to load up the whole world and aren't sharing things with everything else
I'd love to be proven wrong but I feel like if you use e.g. Qt you're gonna have to hold onto a bunch of stuff that you wouldn't if you were "just" using OS-native stuff (though maybe that gets shared if you're using the exact same version? Is there something that can be done in this space?)
As an additional data point, I recently vibed an egui wrapper around a library I wrote for mod management for a game, and testing it out now, it idles at 92 MB. This implies to me that at least half of the overhead is probably not from the gui framework, but I also don't know how much effort they spent trying to optimize it; I didn't try to optimize my vibed GUI app at all, but I did hand-write the library that it uses for file management, state tracking, etc., and I tend to go out of my way to try to avoid unnecessary allocation in my Rust code. I don't know how much of the memory usage is essentially required overhead or from other dependencies for non-GUI parts of the app, but my instinct is that there's probably a bit of optimization that can be done. I don't think it's crazy for them not to have spent the effort on trying to do that yet though (or potentially even at all, if it's efficient enough for their own personal use).
With Qt, on my KDE Linux, a simple app usually stays well below 60 to 100 MB.
Just tested, mine is 400MiB RSS. I was expecting less :-/
I just tested a simple Qt app on my Linux KDE Neon and it consumes just ~32.3 MB RSS. Simple Qml app memory consumption is ~120.4 MB RSS.
$ ps -o pid,rss,command -p $(pgrep -f SimpleQtApp)
PID RSS COMMAND
1471929 33052 ./SimpleQtApp
$ ps -o pid,rss,command -p $(pgrep -f SimpleQmlApp)
PID RSS COMMAND
1478335 123260 ./SimpleQmlApp
// Following is the simple Qt app code.
#include <QApplication>
#include <QWidget>
#include <QLabel>
#include <QPushButton>
#include <QVBoxLayout>
int main(int argc, char argv[]) {
}// Following is the QML app code
#include <QGuiApplication>
#include <QQmlApplicationEngine>
int main(int argc, char *argv[]) {
}// Main.qml
import QtQuick
import QtQuick.Controls
Window {
Sure. Sorry it wasn't clear; I meant I just tested the Telegram desktop app for Linux.
> Is it just me or does anyone else feel that 200 MB is a lot for a native chat app written in Rust ...
That was my first thought. But considering it as a significant improvement from > 1 GB, I guess it is what it is.
> I remember back in the day, apps like Miranda IM (and early versions of Trillian) used only digits of RAM ...
Sadly this was true for many apps.
Looking forward to the 2030s when we get a wave of lightweight actually native software as an alternative to the bloated Rust rewrites ;)
How would you you do that—chucking libc out the window? A monokernel?
"Claude, write me a client for WhatsApp in raw assembly"
I just checked with the native WhatsApp client on Windows 11: 650 MB of RAM as it is running, across all its processes. Thus, taking ≈⅓ of RAM is nothing to brag about for a reimplementation that focuses on being lean and fast. Also, "opens in under a second" – back in the days when SSDs where new, programs opened instantaneously (<60 ms)!
Lastly, I still have to be convinced that Rust is a good choice for GUI programs, considering their messy mutable state and ownership.
Hello world in Rust is huge, and every actual program I've looked at installed dozens of packages for basic functionality.
Turns out all those zero cost abstractions add up to a lot!
The number of packages doesn't have anything to do with this
It does with the compile times lol
Is there actually a way to see a breakdown of memory usage for a program? If you want to see where all the memory is going?
> Is there actually a way to see a breakdown of memory usage for a program? If you want to see where all the memory is going?
Flame graphs are a pretty common tool for this (maybe slightly less common than using them for seeing the breakdown of the time spent when running).
The topic was ram usage during runtime.
What causes that?
You're welcome to demonstrate otherwise
yeah 200MB is nothing to boast about
Matrix bridges for sup, signal and the rest are good enough to never use the web client anyway. You can also skip the part where you need to have it installed on the phone by running waydroid (if you can figure out how to scan qr codes with it).
dont get me wrong, I like the extra performance, but every single alternative whatsapp client has the same issue where it's missing enough core features that you end up needing to go to the browser version often enough to be a nuisance and I end up just using the browser instead (which I hate, I really really would prefer a performant client instead!)
Having also been through a similar journey, which features are missing from this one?
I use this:
Feels like you're just a serial complainer.
Egui is pretty bad idea. It uses "immediate mode" rendering which means whole window is redrawn on every mouse move. I ran PhotoCraft (built in Rust + egui) in a VM wihout a GPU and the UI felt like it was running on 3 fps. If you use egui, try running it without a GPU before releasing.
Egui is definitely not what you want to use on a 4K screen. It is only good for tiny screens of embedded devices.
Why there is no reactive UI that tracks all dependencies and redraws only what needs to be redrawn? (not React, it also re-calculates (but not redraws) everything on every change).
Also why does it visually look like bad version of Telegram? And Telegram can run without a phone present.
> Why there is no reactive UI that tracks all dependencies and redraws only what needs to be redrawn?
There's plenty of them. Slint, Floem, iced, Vizia, fltk etc. Slint and fltk in particular also exhibit excellent performance and very little resource usage even without a GPU.
eframe is reactive by default, so it only repaints on input/animation, mouse moves count as input technically though so you get a pass on hover
What is the argument here?
Basically every device has a GPU.
Why is it bad on 4K?
Did you measure anything in a real setup?
I disagree. First, not every GPU supports Vulkan and other modern standards, and not every GPU even supports executing code. Drivers are often buggy/unsupported. Even if there is a GPU, compiling shaders takes time and CPU must be used in the meantime.
Finally, for app to have access to GPU, it must run on a host unrestricted. Why would you take somebody's code from Internet and run it unrestricted, violating the principle of minimal pivileges? That does not sound smart, especially if you have a crypto wallet on the same computer. Those who do not use VM or sandboxes will sooner or later learn this.
> Did you measure anything in a real setup?
VM is a real setup. Why would I run third-party apps without a sandbox?
Also, today we have an advanced AI that is capable of solving science problems. Should not be difficult to build a GUI that works fast without graphic acceleration, right?
Finally: the modern DDR4 DRAM has approximately 40-50 Gb/s bandwidth. Updating 4K screen at 120 Hz requires 3840 × 2160 × 4 (actually should be 3) × 120 ≈ 4 Gb/s. No problem at all.
> Basically every device has a GPU.
Many VMs and remote desktops don't. (Or can't really make use of)
This is an app that connects to your phone and sends messages via the app. I don't think it's that crazy to decide that running on a VM or remote desktop is out of scope.
It doesn't connect to your phone, it just authenticates via the app. I deal with a company where people use thin clients that run WhatsApp on the remote desktop. It's not an unusual case.
Interesting, I apparently skimmed the "Link to your phone" section too quickly (and I guess have a different sense of what that phrase implies than the author of that README, since a "link" that no longer requires the other end to exist anymore doesn't really seem like a link at all).
It is a potentially unsafe app from some random person that can backdoor your computer so it doesn't make sense to run it without a VM.
>What is the argument here?
it's an incredible waste of resources, especially at high resolutions, to redraw a Gui application like you would a videogame at 60 FPS. These immediate mode UI frameworks were made in particular for that case, to be embedded in real time software, not for a UI where the state is idle or changes only occasionally.
You only redraw when there’s interaction. In exchange you use basically no memory for state retention which frees up the real resource constraint.
Redrawing the whole thing consumes resources. That's power and resources not available to other tasks. There is value in being clever with what you draw.
Yes but it comes at the trade off persistent memory usage. It isn’t just free, and depending on the application in question that may be a lot better trade to make if, say, the app runs in the background or is rarely interacted with.
Moving the mouse is an interaction because there are hover effects.
The argument is that it's wasteful? Even if I had a GPU, I'd rather use it to do inference for insurance rather than drawing a simple UI?
Why do I have to state the obvious like that?
I vibed some code using ImGui and it had this problem. I made it so that it only redraws when data changes with a fixed refresh rate and it went away. So it's not a permanent state of affairs.
PDFCraft works fine for me on a 4k screen connected to an older laptop with an integrated Intel graphics card, blazing fast and smooth.
I am using it on a 2017 intel macbook and its faster than anything else on that device
React doesn't re-calc on every change either if you use memoization and such properly.
To use memoization you must use immutable structures (otherwise React is unable to detect changes) which are a pain to use and are slow if not designed properly. Do not believe me, try designing for example an algorithm that accepts a huge immutable sorted list with keys, a large sorted list of bulk deletes/inserts and produces a new sorted list with minimum operations. I made 2 or 3 prototypes and they still are not good and not even working properly.
In my book, a good UI framework simply attaches to a mutable model made of arbitrary objects, detect changes and displays it with minimum number of operations. Doesn't require to use any proxies or immutable data or store data in components. Shouldn't be difficult. Why nobody made it, I do not understand.
This is incorrect. You don’t need to use immutable structures to have stable references which is what matters.
Use context liberally instead of plumbing things through prop’s needlessly and you’re halfway there.
React isn't immediate mode by my understanding.
In my head it's retained mode + the diffing layer, which sounds the same but if you try to write an "immediate-mode" API (say, using hooks) in React you'll find yourself churning a lot.
At least unless you use the magic React compiler that memo-izes everything correctly.
nothing stops you to render gui at 5 fps. most people won't notice
> Why there is no reactive UI that tracks all dependencies and redraws only what needs to be redrawn?
Nowadays the focus seems to be on video game-style interfaces that redraw every frame. The justification for this is typically that computers are so fast they can now come up with the entire interface every frame, so why not take advantage of that and forget all this retained-mode complexity?
They don't realize that this is a classic case of the developer's machine fallacy, where the developer has a machine so vastly more powerful than any of their users' that they produce a terrible experience for said users. This is also why games these days typically require upscaling even on 5090, because developers usually have that or something even more powerful and they think the bleeding edge is pushing even THAT machine to its knees.
Developers should be testing their software on the most entry-level, bottom of the barrel Chromebooks from 2015, running the heaviest and most bloated operating system they can think of. If people still optimized their software for that, then maybe computers would still feel almost as fast as the Apple II from 1977.
https://danluu.com/input-lag/
And obviously all computers have infinite capacity batteries to maintain game-level power consumption.
Depending on what you're doing GPU accelerated rendering is more battery friendly than CPU rendering though.
How long can a phone run on a battery when playing games? A day? Or an hour? Clearly shows how "efficient" GPU is.
I mean, if the game used CPU for rendering, it would last even less long.
Drawing the entire interface is more expensive than drawing only what changed, though. You don't have to give up the GPU for that.
The GPU will re-render everything anyway. What you can at most optimize is the upload of data to the GPU (i.e. upload only what has changed).
Also consider that if your UI framework supports z-level, opacity and other features like that then determining what has changed for rendering is much more complex than just determining what UI elements have changed.
That's actually a very good point, I haven't seen any care for power consumption from software developers in many many years. The only people who seem to still care about it are hardware developers like Valve and Apple. I admit I never thought about it myself either.
I would figure that doing less work generally requires less power, but some developers are crazy and act like they own the whole CPU, generate tons of heat, stress out the cooling system etc. with multithreaded bullshit that did NOT need to be multithreaded.
Not sure why multi threading is a victim. It really depends.
It does indeed depend.
Some multithreaded workloads will use the full logical processor count to pin every core and that can really suck on low-end systems. I think aside from balancing multithreading overhead, this is one of the reasons why some more advanced software (such as 7-Zip) lets you select the number of threads to use for a workload, even if you already know and accept that it'll be expensive until it's completed.
Lots of multithreading things I come across as a developer have a default of something like 4 threads, or only use a certain fraction of logical cores up to a certain maximum, etc. because it's generally more polite not to always pin every core.
Or are plugged into a world with infinite quantity of renewable energy.
For any vibe-coded open-source project, shouldn't the prompt history and token costs be published as well?
What purpose would that serve? You have the source code. In the old days we’d just share tarballs. No provenance. It’s fine. You have the unit of legible modifiability.
In the early days of AI coding someone did publish the prompts and it was utterly useless to me https://github.com/i365dev/LetterDrop
The source code itself is a sufficient prompt.
There have definitely been times when I've cloned repos that were vibed, pointed my own agent at it, and then hacked up whatever changes I've wanted. I don't think there's been a single time that a lack of prompts has caused any issues, but there have been at least a few times where stuff like AGENTS.md checked into the repo has caused hiccups from them encoding stuff that conflicts with how I want things done.
it seems like we're entering the next phase of "written in rust": UIs
Looks great, but... how can one trust it with credentials/communication? (nothing against the developer, more the principle of the thing)
ummm, you can read the code...
but you shouldn't trust these unofficial clients, easy way to get your whatsapp account banned
Yes, it would be great if we could set up our own test WhatsApp server.
It's called an XMPP server.
Good thing all my friends are already on XMPP server!
Also, I looked at how dates are written in a screenshot and thought that "2 days ago" would be so much better than "Tuesday". Because you do not have to compute in your head how many days ago Tuesday was.
Sounds reasonable, but IME apps that use relative timestamps switch to absolute time past certain threshold, and then I end up with two adjacent entries "14:38” and "15 minutes ago" and scratching my head.
Signal does that and I hate it when it happens.
There are other minor problems as well:
- Screenshots don't age well: you need to know the screenshot time and do math
- They need to be maintained, which means the screen keeps updating even if nothing else is happening
Claude Code: "Heads up. At this pace you’ll run out Sunday night, before the Oct 14 reset."
It is silly to mix the two. I usually display the relative time and offer a timestamp on hover or if there's space, show both.
For an easy-to-read chat list, I chose in a recent tui application to adapt to the age of the message and write only the hour for today's messages, "Yesterday" for yesterday's messages, the week day for 2 to 6 days messages (so this couldn't be ambiguous), month+day for previous messages, year+month+day for last year+ ones. Works pretty well!
I hate relative timestamps, I find it much easier to remember specific week days, so I very much prefer this style so I don't have to compute in my head which day of the week I got the text.
Anyway, I tried this application and it seems to mix different styles depending on how long ago you got the text: "yesterday", "Friday", "18 Oct 2026".
I presume if I use this my phone number will be blacklisted from WhatsApp.
That's the annoying thing with WhatsApp, Slack, Discord, etc. Let's say I've got a personal client (that I'm definitely not using...) which works so much better than the official one. I cannot distribute it or use it according to their rules. It's forced enshitification, even though we have better options.
On the good side though - if you're replicating the official behaviour close enough... maybe nobody will know. But then you have to make sure everything, including key sort order, and JA4 of requests matches. And that's tough...
You don't have to follow their rules but if you don't then you need a backup plan in case they ban you. You need that anyway since people get banned at random, but you especially need it if you're intentionally breaking the rules.
In their own README:
> Using an unofficial client may be against WhatsApp's terms of service and could get an account suspended.
Same for all of these unofficial clients.
It’s really a shame that all of these unofficial clients are like this. APIs are APIs, if they’re on the public internet why can’t anybody call them? If there’s potential for abuse then that should be secured server side anyway, since needing a unofficial client isn’t going to stop hackers
It's irresponsible that the warning is hidden down in "Acknowledgements" and if you go via the homepage to download there's no warning at all.
I think this doesn't apply to European users, as WhatsApp announced around one year ago that under Digital Markets Act they were required to allow interoperability with third party providers [0].
0: https://www.whatsapp.com/legal/dma-notice-non-users
I actually wish they'd delete the warning so then anyone who gets banned from WhatsApp for using an unofficial client would have a more legit cause of action against WhatsApp. Meta wouldn't be able to defend themselves with "well you were warned" if you weren't warned.
Oh, but it's in Meta's ToS of course! Didn't you study those before agreeing to them? /s
Dammit. I installed it, it worked beautifully, and now I don't want to risk it.
Eventually the unofficial client gets "fingerprinted" and its over. Its easy to remove the suspension, though. I vaguely remember it was through email.
Eh, there's no humans any longer IIRC. It's all down to whether their support AI blesses you or not.
I got banned for trying to move my chats from Android to iOS using the app rather than the special tool I didn't know you were supposed to use. I was lucky I eventually got unlocked.
I want a decent WhatsApp client that doesn't crash constantly and where you can search properly, but it's not worth the risk of getting banned again.
Too bad. WhatsApp might be a reasonable service if you could trust the client not to spy on you.
Not supporting calls is a dealbreaker for me Also doesnt whatsapp ban you for using 3rd party clients?
It's a bit basic. I installed it and then uninstalled it.