Glad that works for you! With my bank (comdirect.de) I can use a mobile website, and if I were to use something AOSP- or Halium-based, I could also use their PhotoTAN app, which, as the name implies, needs a working camera in Waydroid (on my OP6 with pmOS, the cameras work via libcamera, but not in Waydroid), so I have a small gadget for all these TANs.

My main worry with the “let’s just use Play Store/Aurora store and the run that apk”-approach is that it does not really send a visible signal to banks that they need to keep considering customers that don’t use Android proper.

It also always means that the next update (e.g., after some consultancy or some audit happened) may not work any more, meaning, access may be revoked at any time. Complaining to customer service or in Play Store reviews may have an effect, but it will still hurt. I think I would feel a tad safer if a banking app lived on FDroid… but sill.

I hope this gets my point across.

As someone who spent some time on the topic (result), it’s not that every new app is adaptive. Even if someone uses the nice new widgets of libadwaita (or previously libhandy (GTK3)), that app is not necessary running well on mobile if width-reqests demand a higher minimal width or content is just too wide.

The same is true for QtQuick Components or Kirigami, which are the equivalent for adaptive Qt apps.

That said, yes, many new apps developed with these technologies work fine OOTB without the developer even knowing; and if they are too wide or tall, fixing that is usually rather simple and not a full rewrite/redesign.

Not directly, here’s what we have:

https://linuxphoneapps.org/categories/maps-and-navigation/

Of these, at least PureMaps does turn-by-turn - as a no-car-person that last drove in meaningful way when paper maps where a thing, I am the wrong person to ask about car navigation stuff.

Additionally, there’s the OrganicMaps desktop flatpak (not a great experience, only good for seeing where you are) and zooming around. Fortunately, a work on a mobile-friendly Kirigami app for OrganicMaps has been funded by nlnet.

Also, runnning some web Maps in a browser (e.g., via https://linuxphoneapps.org/apps/dev.heppen.webapps/) is always an option (e.g., for browsing Google Maps for an open restaurant nearby).

Just 2ct’s on the banking thing (sorry if it sounds rude, but I just can’t hear it anymore):

Just forget banking apps of you don’t want to stay on iOS or proper Google Android forever and ever and ever, even AOSP-based OSes struggle with that (a lot).

Go to a bank that still has a proper website and allows some kind of hardware device for TAN (and tell them that this is why you are leaving/joining) - we need to show market demand for alternative solutions or else these will disappear completely over time.

We also need to make regulators/politicians understand, that taking part in life must be possible without owning a device blessed by Google or Apple. We really need laws here.

Regarding Android apps: I hope that https://gitlab.com/android_translation_layer/android_translation_layer will make a difference here going forward. A Wine-like approach is just so much less of a resource hog.

Regarding the Camera on the PinePhone Pro: It somewhat works by now, if not on every OS. Be it with libcamera or Megapixels 2, we’re getting there. I suppose it’s just that nobody told the Wiki.

+1 for the Surface Go 2. I use on of these with NixOS GNOME, and it’s lovely. For Pen use I like Rnote. You could also use Plasma Mobile on it. The Go 3 is not really better, so don’t get it unless it is in the same price range, and avoid the 64 GB eMMC model.