Yeah I kinda agree with TS. Maybe the app should trigger a notification when it detects that the phone android version is already the minimum supported version.

"hi loserguy, this is the minimum supported version of android liao. Time to make muka Kecian and see if your kids will buy you a new phone."

Not really. How many users actively check for the latest update number on their phone or computer? It is only when there is a problem that people check, myself included.

A better way will be to notify the user that this is the last supported version when the app updates. While the app is still functional.

e.g.
1) Last supported version android 10.
2) App detects user is running android 10 during update.
3) Notifies the user to start shopping for a phone before last supported version is increased to android 11.

Security vs convenience.

But yeah, I would prefer a separate app just to generate the TOTP for all the banks. No need to tie in with all the security requirements if that app has no direct access to your banking account.

That or passkey login via browser and browser based apps for bank transactions. Instead of one app for one bank

yeah, but for many banking apps no choice, they won't allow you to use an old version of the app

personally, I think the problem is the banks trying to cram every stupid thing in their app. why lar are they reinventing the wheel.

TOTP authentication is already well established.
Passkey authentication doesn't seem that complicated.
Both allows the bank to revoke the authorizations for that secret key/passkey if the device is compromised.

tldr, bank bodo. sorry for the rant.

You don't understand. The notification was a blanket notification for ALL users regardless of the android version they are running.

An android 8 user will receive the notification, so will an android 13 user. It places the onus on the user to check for themselves, even when the info is visible to the app via API version numbers.

This is like bulk sms notifications, most users will ignore it because, they think, it doesn't affect them.

A better way for the app developers will be to push notifications to those who WILL be affected. Do it everytime the app is started. Not a notification asking them to check for themselves if they will be affected

translation: hey mom look, i took stuff away from devs again and convinced them it was a feature

to be fair you can't take stuff away if it was never there in the first place

Please don't justify bad design. If a junior programmer showed me this I would still correct him the same way.

Too many notifications and you get complaints. But not enough and you get problems like this.

The easy solution is to annoy the heck out of the 10% of users still clinging to older versions but leave the majority alone. Show them nag screens every time they start the app.

At the end of this period, you should get the numbers down to a reasonable number 2-3% if you are lucky.

Update the app with a new notification one week before the major update goes live. Ask the 2-3% to come get the hardware token.

Edit: dev bodo macam manalah nak maju

This post has been edited by loserguy: Jun 25 2023, 03:24 PM

Normally companies look at customer retention and satisfaction. This is not something difficult to do on the app developer's side.

Compare that with how much the bank is spending on customer acquisition campaigns and the shitstorm because the update went live over the weekend when most branches are closed.

Maybe close unnecessary accounts, just stick with one or two banks.