cross-posted from: https://sh.itjust.works/post/42943610
Taken from the readme of the app on github:
The current release provides only basic functionality, with several key features to be introduced in future versions, including:
App and device verification based on Google Play Integrity API and Apple App Attestation
Additional issuance methods beyond the currently implemented eID based method.
These planned features align with the requirements and methods described in the Age Verification Profile.
There is an issue opened to remove this as it’s basically telling us that to verify our age in the EU an American corporation has the last word, making it not only a privacy nightmare but a de-facto monopoly on the phone market that will leave out of the verification checks even the fairphone (european) with /e/os.
There’s a big difference between a reference implementation and a proof of concept. A proof of concept just shows it’s possible at all, but a reference implementation is meant as a reference for “you should do it this way”. Expect most companies to just directly copy the reference because they’ll feel it’s a waste of time developing their own system that’s in compliance.
Sure it’s beyond a proof of concept and others will definitely heavily rely on it yet my point still stand, i.e no one is supposed to install this built app directly. As I also said yes it’s wrong to rely on Google and Apple in general but even more so with talks of EU sovereignty so I’m not giving them any slack for that. What I’m still insisting on is that this repository is not the app people will have to use.
This is definitely going to be copy&pasted as a foundation in many EU states. Therefore, that it requires Android and iOS at all, let alone Google Play, is a fundamental error. Some people avoid smartphones for good reasons, yet still access parts of the internet that may apparently soon be gatekept by this new age verification mechanism. Also see here.