Problem is this requires turning off protection for unknown origin apks and these days many banking apps etc stop working once you do that.
Could be useful for a spare phone for secure but non critical work.
Could be useful for a spare phone for secure but non critical work.
Is this like, to send money, zelle, CashApp sort of things you all keep talking about?
Can't you just use the browser on your phone to interact with the bank? The browser doesn't know its rooted, does it?
You could set a clock by the "but my banking apps" every time Firefox or F-Droid or Sideloading comes up.
I don't carry a wallet, my banking app supports NFC payments.
I'm pretty sure you can only be born once.
I guess it could be "Google Wallet, né Google Wallet, rené Google Pay".
Speak for yourself! Google's products are eternally trying to escape Samsara through a product cycle of death and (sometimes) rebirth.
It sends me notifications when money arrives or is spent. Scanning a QR code to pay for something is much less clunky than doing the same in a browser. And it integrates into my phone authentication system so I only need to scan my fingerprint to open the app instead of remembering a password and waiting for a one-time code.
What do I do on the app? I check the balance on my accounts, I move money between my accounts to get more interest, I pay for my kid's remedial classes, I pay my trainer, I scan QR codes to pay online when the shop provides this payment option so I don't have to type in my card details, I check my virtual card details when I do have to enter them, I buy and sell stocks.
All this is possible in browser nowadays. And scanning QR codes doesn’t have to be clunky – it’s just that developers are sloppy.
To each his own.
it's all so reminiscent of "you must use IE6 to access this site"
https://www.straitstimes.com/singapore/uob-dbs-introduce-new...
As for getting upset about sharing a phone with unapproved apps, I think this is a failure of sandboxing. The app should see as much of the phone as I want it to and no more.
These days banks have KYC and should know who finally gets the money. Even across borders except perhaps in North Korea etc. for those countries that don't co-operate entire SWIFT system must be blocked.
But for some reason they try other things, blame users but never claw back
From a security perspective it makes sense. If an app actively abuses such information it would be easy enough to hide it in a future build. The only way around that is an attestation scheme such as SafetyNet.
So the 3dparty component doing the "security" check for the banking apps is a little overzealous.