[Alpha] Greenline - A qml Whatsapp client for Ubuntu Touch

StephPTi

Thank you very much for this app. I have everything i need so far and its working well and very fast. until now, the battery usage is also good .

brenno.almeida

Thanks for the feedback you all, any issues please report.

We have a new release: https://github.com/brennoflavio/greenline/releases

Experimental support to record voice messages. Give it a try and report if it works for you
Support for messages with images and buttons
New icon and splash screen
Support for deleted messages, both seeing deleted messages and deleting your own messages

Linus67

Hi @brenno.almeida

First of all, thank you so much for your incredible work on Greenline! Seeing a native QML WhatsApp client moving forward so quickly on Ubuntu Touch is amazing. The recent alpha builds with voice messages and message deletion show huge progress.
As a tester, I noticed an interesting behavior regarding the main chat list:
The app currently populates the history with every single JID (Jabber ID) available from the server's sync history. This includes old "ghost contacts" (like one-time marketplace buyers), unknown numbers, or old groups that were long deleted or left on the main device. When you click them, they just show an empty chat view.
I suspect that filtering these out isn't a quick "one-click" fix, as the underlying protocol/daemon likely dumps the raw cached stream of all historical chat channels upon connection, without the local filters that the official Android/iOS apps use.
Since you are probably busy with core features, I was thinking about some pragmatic ways to tackle this on the client/UI side whenever you find the time:

Frontend Filtering (QML Delegate): A quick visual fix could be using a filter or modifying the ChatDelegate in QML. If the model's row indicates that there is no lastMessageText (or the timestamp is null), the item's visibility could be set to false and its height to 0.
Database Query Filtering (Backend): If Greenline stores the synced chats in a local SQLite database, modifying the SQL query that populates the QML model might do the trick (e.g., SELECT * FROM chats WHERE last_message_id IS NOT NULL OR unread_count > 0).

Just wanted to share this observation and some ideas. No rush at all—the app already looks and feels great for an alpha state!
Keep up the fantastic work!

P.S. (Added positive note):
Actually, having this long history of contacts has a surprisingly positive side effect! It acts like a historical WhatsApp-specific phone book. It's amazing to see how incredibly fast, reliable, and battery-friendly Greenline already runs after just about 3 months of development. It’s a massive upgrade compared to the sluggish, battery-draining WebApp solutions we had before. If you ever decide to filter the main chat list, maybe this "raw list" could be repurposed into a dedicated "WhatsApp Contacts/History" tab in the future?

Linus67

One more thing:
In its current state, Greenline is actually the PERFECT messenger for children!
Since it focuses purely on communication without all the bloated social-media distractions like Channels, Communities, or Status tabs, it provides a safe environment. Plus, keeping the contact history ensures that old group connections (like school or sports clubs) aren't lost and remain recognizable.

Thank you for building such a clean, fast, and battery-friendly alternative!

pparent

@brenno.almeida

Would you consider doing a confined version of the app without a background deamon, and with the go part only running when the app itself is running? I think it would be usefull for those who don't want notifications all the time, and don't want their battery to be drained by the deamon or are not comfortable with having a whatsapp deamon running at all time. And it would be easier to publish on the openstore!

Thank's a lot for your work!

ChromiumOS-Guy

you need to add the ability to send files, you currently don't have the option so i cannot upload a .pptx for example.

brenno.almeida

@Linus67 The chat list is the source of truth for contact information, there's no separate list of contacts in this app. This makes the code easier to undersand and with fewer moving parts, but the tradeoff is that to render the person name in the group it needs to exist as a individual in the list, so removing chats is not possible.

This is unlikely to change, would add a complexity I don't want to manage. However I do plan to add basic filtering in the list, similar to how Teleports works, which should mitigate this.

brenno.almeida

@pparent No plans for a confined version, mainly due to the burden of mantaining two versions of the same app. The best move here is to work with UT devs for proper support of backgroud services for click packages, so this app can run confined as is.

Support for pausing the daemon when app closes is planned tho, which achieves the same result I think.

brenno.almeida

@ChromiumOS-Guy contributions are welcome! But support for all message types is planned before going beta

StephPTi

i just found something. i deleted a whole conversation thread on my whatsapp android but i still can see it on greenline and i cannot delete it. i had this behavior on other whatsapp web based apps

Linus67

@StephPTi
Now you can see in Greenline: Meta stores all your actions on WhatsApp. If you like a comment in a group, that contact is stored in the database linked to your phone number. You can view all these records now in Greenline.
You now have a complete list of the phone numbers (contacts) to which you have ever reacted or commented. This is part of the metadata that WhatsApp stores permanently on its servers: when you interacted with whom. This means that most of what you delete in WhatsApp is simply hidden.

In a future version of Greenline, it may be possible to hide this ‘metadata’.