You don’t have to configure KDE you know. You can just keep the defaults like you’re probably doing with GNOME.

It does!

You’re right, you can’t run the Android (or iOS app) twice. If you want a second device running WhatsApp you’ll need the web app.

I definitely hope so, so far it’s looking promising!

I think installing all those dependencies by hand is not a good solution in the long run.

Well, no. “In the long run” this gets packaged by distributions so you don’t have to compile anything. Right now it’s available for Alpine Linux and there is an AUR package for Arch.

Wasn’t there supposed to be a flatpack container to be downloaded somewhere?

There is a Flatpak (no c in that name!) base app available, and Newpipe has been packaged with that as a Flatpak, see https://flathub.org/apps/net.newpipe.NewPipe Ideally we get more stuff packaged up once more works but I don’t think it’s feasible to repackage everything out there so for a lot of applications you’ll just have to have a locally installed ATL outside of Flatpak.

You were responding to a comment talking about Ubuntu Touch. You then talking about “we” without any explaining of who you meant made me assume you meant Ubuntu Touch users.

The OrganicMaps for “regular” Linux is very different from the Android app though. Completely different UI tech (Qt vs native Android widgets) and lacks important things like turn-by-turn navigation.

It translates the Android API to Linux desktop-compatible calls, just like Wine does for Windows apps.

This is not about Newpipe itself but more that fact that this is an Android app ran on desktop Linux, without any containers like Waydroid does. This is like Wine, but for Android apps.

Ubuntu Touch can’t use GTK? Why not?

Well yes, it’s still early days and very much WIP. But the fact it works at all is amazing and shows what can be done with more work.

Note that the actual latest release is 1.2.5. This is just a patch release for the 1.0 series.

Eh, I have used KeepassXC over multiple machines using NextCloud to sync it for years now and have never had any conflict.

Canonical might only care about Snaps, but like I keep saying you can just enable Flatpak and get it from there. Only if you want debs you’ll have to move away.

But KDE never will be exculsively available as snaps. Again, you can just install Flatpak and get them from there. Or get Debian and stick to .deb, it’s largely the same base as Ubuntu anyway.

You can as of yet still disable Snaps entirely on *buntu and enable Flatpak instead. I doubt you’ll be getting them as regular .deb packages for long still though…