(btw you can run all android apps on OS built on the android open source project like GrapheneOS or LineageOS. Banking apps also work perfectly on GrapheneOS, don’t know about LineageOS, not using it)
Have you not seen that google is apparently going to limit the ability for grapheneos?
By YOUR metric #2 IS #1. If you go to grapheneOS, you are trusting that one they won’t enshitify and two that google won’t absolutely wreck the ability to continue.
lineageos is still based on androids kernel. It still has connectivity to google applications.
(btw you can run all android apps on OS built on the android open source project like GrapheneOS or LineageOS. Banking apps also work perfectly on GrapheneOS, don’t know about LineageOS, not using it)
Not entirely clear unfortunately. #2 requires google to continue to allow APKs to just work on the open OS’s. If they decide to require google signed OS components and/or encrypt the APKs, we’ll be at the mercy of the individual developers to continue to compile for FOSS. Banks will be far less likely to release ‘less secure’ versions of their apps to run on ‘aleternative operating systems’
For now, 2 is a good answer, but looking toward the future, stuff is looking a bit bleak. It’ll be a slow downward slide into obsolescence if we can’t keep the developers interested in FOSS support and if they’re no money in it for them, we’ll always end up with the shit end of the stick.
Company A enshittifies
Options:
The choice is clear for me.
(btw you can run all android apps on OS built on the android open source project like GrapheneOS or LineageOS. Banking apps also work perfectly on GrapheneOS, don’t know about LineageOS, not using it)
Have you not seen that google is apparently going to limit the ability for grapheneos?
By YOUR metric #2 IS #1. If you go to grapheneOS, you are trusting that one they won’t enshitify and two that google won’t absolutely wreck the ability to continue.
lineageos is still based on androids kernel. It still has connectivity to google applications.
Not entirely clear unfortunately. #2 requires google to continue to allow APKs to just work on the open OS’s. If they decide to require google signed OS components and/or encrypt the APKs, we’ll be at the mercy of the individual developers to continue to compile for FOSS. Banks will be far less likely to release ‘less secure’ versions of their apps to run on ‘aleternative operating systems’
For now, 2 is a good answer, but looking toward the future, stuff is looking a bit bleak. It’ll be a slow downward slide into obsolescence if we can’t keep the developers interested in FOSS support and if they’re no money in it for them, we’ll always end up with the shit end of the stick.