Yeah, this feels like a huuuuge drawback to me. You are immediately prevented from creating an implementation which works on Windows/macOS/Linux, and it is rei

Yeah, this feels like a huuuuge drawback to me. You are immediately prevented from creating an implementation which works on Windows/macOS/Linux, and it is reinforcing the Google/Apple duopoly in the smartphone market. Moreover, you are relying on "trusted execution" remaining unbroken in thousands of different dirt-cheap smartphone models. It's not a question of "if" it gets broken, but "when". And revocation isn't exactly an option either, because you risk leaving millions of people unable to use your government-mandated app. I believe that applications like these should be explicitly designed around the possibility of the user device being compromised or a malicious third party interacting with it instead - even if that means a loss of functionality. And while you are at it, make it fully open source to make it easier for the security community to review it for silly things like the self-rolled crypto we see here.