[BlueTemplar]

It's still based on Android though - so isn't it building on sand ?

Isn't it better to focus our efforts on projects unrelated to Android, especially since some viable ones have appeared recently : Librem 5 and especially PinePhone.

[OfSanguineFire]

Banks in many countries require an Android phone for online banking. Even if they offer an online-banking website that you can access with any browser, you may still need the Android app for 2FA. This is one of a number of reasons why the PinePhone or Librem is unfortunately not a daily driver. Also, things like paying for parking or interacting with public services are moving to Android apps in some places.

[BlueTemplar]

Is that even legal ?

Banking and public services are too important to be restricted to people with smartphone ownership (even regardless of OS).

It's even more important to refuse to use them, publicly shame them, and complain about them failing at their duties.

[lmz]

Before smartphones some banks used a hardware token to authenticate web transactions, but now that is being moved to (non rooted) smartphones.

[tmtvl]

I was given a hardware device by my bank to do my online banking. If they want to move to smartphones I expect them to provide me one of those as well.

[OfSanguineFire]

One of the very reasons banks have been phasing out hardware tokens (and code cards) is because they represent a cost. Of course the bank is going to put the price of the smartphone all on customers.

[Kwpolska]

Don't most banking apps reject non-GooglePlay/unofficial-image/rooted phones?

[Arnt]

Yes, and the reasons are instructive.

When you get to the lowest level, technically, the banking apps want to store files on the phone that the user can't access.

This means that something like lineageos can run banking apps, if the phone tells the banking app what the app wants to hear. It's fiddly but can be done, and in fact it is what I do on my private phone. It also means that a platform that fundamentally gives users the right to read all the files on the phone (ie. to make a complete backup) will not be supported by banking apps, because such a platform will not let the banks do what they think they need to do.

I think this implies that such platforms can't grow beyond a niche within a niche.

[user_7832]

While I can understand Google and the banking apps' actions, it doesn't make much sense given how PCs having root is hardly every a concern for a bank. If you can do something bad with banking on a rooted device, it's probably doable on a computer too.

[OfSanguineFire]

Oh, banks are definitely concerned about PCs having root. There are even some banks that have removed their online banking websites entirely (except, perhaps, for corporate clients) and require customers to do everything through the Android app instead.

[Arnt]

My bank and my wife's bank both require 2FA. On the app, one of the Fs is having physical access to the device (the phone/app, which was vetted by the bank when the app was installed). On web browsers, these two banks don't offer any factor like that.

In end effect, the banks treat a non-rootable device as suitable as a "something you have" factor, but will not treat a rootable device as that.

[fsflover]

Which is why I was switching banks until I found one not forcing me into the duopoly.

[user_7832]

Huh that's interesting, thanks for mentioning it. I wasn't aware of that.

[OfSanguineFire]

One of the draws of GrapheneOS is that, since Pixel phones have a relockable bootloader, that Android image will pass SafetyNet. While Google Play Services is typically required by banking apps, on GrapheneOS you can run Play Services in its own sandbox.

[RetroTechie]

They might, but app for my bank works happily on LineageOS.

Same eg. with app for a local 2nd hand site, which on startup complains that it needs the Google services... and then runs without issue (only appears to use those Google services to pinpoint the phone's location).

Imho this is 1 more reason to put alternatives like LineageOS on a phone: the more users on those, the harder it is for app developers to drop that usergroup for... well, reasons.

[seszett]

Ironically you might have to root your phone to install the necessary Magisk modules to make the app think it's on a phone running the official thing.

[SkiFire13]

Most reject phones that don't pass SafetyNet. There are ways to pass it with unofficial images/rooted phones, although I'm not sure for how long they will keep working and I think you still need Google Play.

[codedokode]

Do not use banking apps on a phone because it is not secure (there is no second factor). Use bank's website on a laptop instead.

[OfSanguineFire]

As I said, for many banks, in order to log in to the bank's website on a laptop, you need to receive a 2FA code sent through the bank’s app on an Android phone.

[mixmastamyk]

I’ve found that many times when a service says this the system will work with any OTP program. They just don’t tell you specifically. Maybe they don’t know, think it’ll confuse, and/or prefer you didn’t.

[anticensor]

Not always, some countries actually require this to be sent over a bank-specific protocol.

[mixmastamyk]

“many times” is roughly equivalent to not always.

[codedokode]

Here (in Russia) typically SMS is used as a second factor and you don't need an app. Requiring to install an app is basically requiring to buy a modern smartphone only to be able to log in.

[DANmode]

Unless you're using a Chromebook or similar device as the laptop, this is kinda out of date, if using best practices.

[npteljes]

It's the regulation that should focus on creating the foundations of alternative systems, not the phone manufacturers. If a bank doesn't have a website, or a govt app doesn't have a website equivalent, then Librem & co is already out of the picture, from the everyday usability standpoint. To provide the citizens freedoms, service providers need to be forced to use open standards, like HTTP & HTML, to serve an standard interface that has all the necessary functionality. No matter how many grassroots initiatives we have, if this is not provided, they are automatically all out of the race.

So really, if anything, I'd like people to focus on regulation.

[jacooper]

No it isn't, as unlike the others, grapheneOS is actually usable and dailyable.

[fsflover]

I doubt grapheneOS requires much less effort to daily drive than others. Sent from my Librem 5.

[ryukafalz]

As an owner of both a Librem 5 and a Pixel 6a running GrapheneOS I can confirm that the latter has been much more reliable and has taken substantially less work to get to the point where I can daily drive it. The Librem 5 is not there yet, and while I would like it if it were I'm not currently very optimistic about that.

[bkallus]

In the past year, I have used a pinephone+keyboard with Arch, a oneplus 6t with postmarketOS, and a pixel 7a with GrapheneOS. In my opinion, Graphene is significantly easier to daily drive because the applications are designed for a phone's form factor.

[fsflover]

Could you share which Pinephone apps you needed that aren't designed for a phone's form factor?

[bkallus]

The biggest one is the Firefox ESR build from the pmOS repos with the custom userChrome.css that tries to fit everything onto the Pinephone's screen. I pretty consistently encountered pop-up prompts (for example, in the built-in password manager) that ran off the edge of the screen in both portrait and landscape. Zooming out sometimes helped, but then the text was unreadable and the buttons too small to press. There was also no forward button in either the overflow menu or the nav bar. The Phosh settings app had similar problems.

[eks391]

There's some hiccups when you first set GrapheneOS up, but after that it is as smooth as, and blends in with, any other Android device. I've never used Librem or PinePhone to comment on them