Chase App doesn't work on new Samsung phones!!!

boingy

Am I the only person that think that a banking app should run on ANY 6 month old android phone?

wmb194

boingy said:

Am I the only person that think that a banking app should run on ANY 6 month old android phone?

No, not when the super cheap ones like the one in question, c.£50, has hardly any RAM and might have a 32-bit OS.

boingy

wmb194 said:

boingy said:

Am I the only person that think that a banking app should run on ANY 6 month old android phone?

No, not when the super cheap ones like the one in question, c.£50, has hardly any RAM and might have a 32-bit OS.

Banking apps are not heavyweight things. They don't require much in the way of memory or processing power. The lack of compatibility is a design decision on the part of the dev team. You could even call it laziness...

Banking apps should run on anything modern and they should definitely run on Android Go, given that many, many new phones are shipping with Go.

wmb194

boingy said:

wmb194 said:

boingy said:

Am I the only person that think that a banking app should run on ANY 6 month old android phone?

No, not when the super cheap ones like the one in question, c.£50, has hardly any RAM and might have a 32-bit OS.

Banking apps are not heavyweight things. They don't require much in the way of memory or processing power. The lack of compatibility is a design decision on the part of the dev team. You could even call it laziness...

Banking apps should run on anything modern and they should definitely run on Android Go, given that many, many new phones are shipping with Go.

No, but the world's moving on from 32 bit and Go 12 isn't even the latest version (14). When you go super cheap you can have problems like this.

boingy

wmb194 said:

boingy said:

wmb194 said:

boingy said:

Am I the only person that think that a banking app should run on ANY 6 month old android phone?

No, not when the super cheap ones like the one in question, c.£50, has hardly any RAM and might have a 32-bit OS.

Banking apps are not heavyweight things. They don't require much in the way of memory or processing power. The lack of compatibility is a design decision on the part of the dev team. You could even call it laziness...

Banking apps should run on anything modern and they should definitely run on Android Go, given that many, many new phones are shipping with Go.

No, but the world's moving on from 32 bit and Go 12 isn't even the latest version (14).

Android Go 12 is only two years old. Banking apps should run on it. And it's not automatically 32 bit. It's designed to make the best of low spec phones, something that banking apps should seek to do too.

wmb194

boingy said:

wmb194 said:

boingy said:

wmb194 said:

boingy said:

Am I the only person that think that a banking app should run on ANY 6 month old android phone?

No, not when the super cheap ones like the one in question, c.£50, has hardly any RAM and might have a 32-bit OS.

Banking apps are not heavyweight things. They don't require much in the way of memory or processing power. The lack of compatibility is a design decision on the part of the dev team. You could even call it laziness...

Banking apps should run on anything modern and they should definitely run on Android Go, given that many, many new phones are shipping with Go.

No, but the world's moving on from 32 bit and Go 12 isn't even the latest version (14).

Android Go 12 is only two years old. Banking apps should run on it. And it's not automatically 32 bit. It's designed to make the best of low spec phones, something that banking apps should seek to do too.

It's a commercial decision. Other banks are available.

clarkey1984

Sorry for the confusion, I am currently on the c02, the x30 returns to me soon, the repair guy is having problems sourcing a genuine screen for it as apparently not many were sold in the UK, I've had the Nokia 8, then the 7.2, then the 9 pureview, then the x30 and obviously the stopgap c02, i really like Nokia phones, i even persevered through the symbian and then windows mobile phases with the N95 and Lumia 1020.

masonic

boingy said:

wmb194 said:

boingy said:

wmb194 said:

boingy said:

Am I the only person that think that a banking app should run on ANY 6 month old android phone?

No, not when the super cheap ones like the one in question, c.£50, has hardly any RAM and might have a 32-bit OS.

Banking apps are not heavyweight things. They don't require much in the way of memory or processing power. The lack of compatibility is a design decision on the part of the dev team. You could even call it laziness...

Banking apps should run on anything modern and they should definitely run on Android Go, given that many, many new phones are shipping with Go.

No, but the world's moving on from 32 bit and Go 12 isn't even the latest version (14).

Android Go 12 is only two years old. Banking apps should run on it. And it's not automatically 32 bit. It's designed to make the best of low spec phones, something that banking apps should seek to do too.

Banking apps would probably run on 64-bit Android Go. The reason modern apps don't work with legacy 32-bit operating systems is that the 32-bit architecture brings with it a limited instruction set, no native support for modern cryptography, a greatly increased code maintenance burden, and risk of vulnerabilities through working around the missing features. The more important security is for an app, the less sense it makes to compromise. App-only banks are at the extreme end of this, as they often lack some of the security features associated with website-based banking. Some rely entirely on the device for security. These are not the apps you want running with a portion of your CPU's capabilities switched off.

[Deleted User]

wmb194 said:

boingy said:

wmb194 said:

boingy said:

wmb194 said:

boingy said:

Am I the only person that think that a banking app should run on ANY 6 month old android phone?

No, not when the super cheap ones like the one in question, c.£50, has hardly any RAM and might have a 32-bit OS.

Banking apps are not heavyweight things. They don't require much in the way of memory or processing power. The lack of compatibility is a design decision on the part of the dev team. You could even call it laziness...

Banking apps should run on anything modern and they should definitely run on Android Go, given that many, many new phones are shipping with Go.

No, but the world's moving on from 32 bit and Go 12 isn't even the latest version (14).

Android Go 12 is only two years old. Banking apps should run on it. And it's not automatically 32 bit. It's designed to make the best of low spec phones, something that banking apps should seek to do too.

It's a commercial decision. Other banks are available.

Essentially, someone with a very basic phone designed for developing markets (e.g. using Android Go) is less likely to be a high value customer. It's the same reason why some apps are made for iPhone only.  

clarkey1984

masonic said:

boingy said:

wmb194 said:

boingy said:

wmb194 said:

boingy said:

Am I the only person that think that a banking app should run on ANY 6 month old android phone?

No, not when the super cheap ones like the one in question, c.£50, has hardly any RAM and might have a 32-bit OS.

Banking apps are not heavyweight things. They don't require much in the way of memory or processing power. The lack of compatibility is a design decision on the part of the dev team. You could even call it laziness...

Banking apps should run on anything modern and they should definitely run on Android Go, given that many, many new phones are shipping with Go.

No, but the world's moving on from 32 bit and Go 12 isn't even the latest version (14).

Android Go 12 is only two years old. Banking apps should run on it. And it's not automatically 32 bit. It's designed to make the best of low spec phones, something that banking apps should seek to do too.

Banking apps would probably run on 64-bit Android Go. The reason modern apps don't work with legacy 32-bit operating systems is that the 32-bit architecture brings with it a limited instruction set, no native support for modern cryptography, a greatly increased code maintenance burden, and risk of vulnerabilities through working around the missing features. The more important security is for an app, the less sense it makes to compromise. App-only banks are at the extreme end of this, as they often lack some of the security features associated with website-based banking. Some rely entirely on the device for security. These are not the apps you want running with a portion of your CPU's capabilities switched off.

I gather from my limited knowledge that 64 bit is more secure than 32 bit, however ,my Barclays app installed and runs without incident, although I am yet to find a way of confirming if my android is one or the other.