Open-sourced the mobile auth layer (no personal data, looking for feedback)
Summary: Anton Minin Baranovskii, Anton Minin Baranovskii, has open-sourced the mobile client of Toqen.app, an access-first authentication system. The key feature of this app is its focus on privacy, as it does not collect personal or sensitive user data, relying solely on device-bound identifiers and cryptographic keys for authorization. The repository is available on GitHub, with the app accessible on iOS and in closed testing for Android. Anton Minin Baranovskii seeks feedback and is curious about whether open-sourcing the authentication layer increases trust among users. The app is suited for various use cases such as SaaS platforms, gated content, and event access systems.
Hey everyone,
I recently open-sourced the mobile client of Toqen.app - an access-first authentication system I am building.
One thing that matters to me here: the app does not collect personal or sensitive user data (no email, phone number, location, etc.).
It only uses device-bound identifiers and cryptographic keys required for authorization - you can verify this directly in the code.
This mobile layer is where access actually gets confirmed:
- user decision
- device signature
- real-time verification
The app itself does not grant access - everything is verified on the backend after the device signs a short-lived challenge.
Repository: https://github.com/toqenapp/mobile-react-native
Product access:
iOS (App Store): search for “toqen.app”
Android (closed testing): https://forms.gle/f9FcbHyHJiajmFWV7
Typical use cases include:
SaaS platforms
gated digital content
memberships
online education environments
event access systems
other products requiring time-bound and policy-defined authorization
I would really appreciate any feedback or honest critique.
Anton Minin Baranovskii
OP3 months agoOne thing I am still trying to understand:
Does open-sourcing something like the auth layer actually increase trust, or do most people decide based on other signals anyway?
Would be interesting to hear how you approach this.