> 1/ One Google Android phone for my banking app with Google Integrity API working Most banks permit using GrapheneOS. It's also possible to do most things via

> 1/ One Google Android phone for my banking app with Google Integrity API working Most banks permit using GrapheneOS. It's also possible to do most things via online banking. Generally only a fcertain things like cashing a cheque requires a native app. > So what I meant is hopefully in the future we will have a GrapheneOS hardware device, but they might also need to fork or leave AOSP. Because trying to be in the Google Android ecosystem and out of it at the same time became impossible or too costly. We're actively working with a major Android OEM towards their future devices providing official GrapheneOS support. Not really clear why we'd need to switch the base for the OS. We'd still need a fork of AOSP if we want Android app compatibility. If we didn't have Android app compatibility, you'd probably have a lot more reasons you couldn't use it as your only device than a single banking apps. Same applies to most users. > I could switch bank for the 3rd time, sure. But how long can I run away? Several European banks have explicitly chosen to permit GrapheneOS via https://grapheneos.org/articles/attestation-compatibility-guide https://grapheneos.org/articles/attestation-compatibility-gu.... We're hoping EU regulation requires Google to stop banning it from banning the Play Integrity API since we provide everything they need to verify GrapheneOS via hardware-based attestation. It shouldn't be up to Google which devices and operating systems are allowed to use mainstream apps and regulators generally agree with that. It's just taking a long time for regulators to understand it and do something about it. We expect it will happen. > We can't spent most of our resources trying fit in instead of creating our own path. We've hardly put any resources into this. There's not really much we can do about apps deliberately trying to stop people using another OS including GrapheneOS. It's more of an issue to solve via convincing them to permit it than a technical one. A technical workaround would only be a temporary hack likely to break fairly quickly.