Passkeys

I’ve been working on this for a while. I’m currently adding passkeys and security keys support to the app!
The app has been based on OTP codes since release, I’m also adding passkey support so that no waiting for emails is needed.
You will still need a verified email in order to sign up, but you will be able to use passkeys for future authentications.
I also think about adding an authenticator app OTP generator to replace email OTPs altogether (for added security in case of a stolen email account), but it’s a work in progress (PS: Again, you will still need a verified email address to sign up).

GitHub Workflows!

This took me ages to build. I implemented workflows and multiple branches:

• Master (Release)
• Beta
• Alpha
• Development
• Testing (no workflows here)

On every push, two jobs run: One updates the website (only on master pushes), and also runs eas update to the specified update branch.
The other job is the most interesting: It checks for version changes in the app.json file, and if the version changed, it starts building a new binary for the app: Signed iOS Simulator (.tar.gz app file), “Signed” Android APK (or AAB if the branch is Beta/Master), and unsigned iOS .ipa file (since I have no paid developer license yet).
The first two are ran through EAS Cloud, and then downloaded by the workflow. The unsigned build runs directly on GitHub Actions’s servers.
After having the artifacts, they get renamed to human readable names, and release notes are automatically generated with the adoption of conventional commits (fix: … | ci: … | feat: … | etc). The script later proceeds to create a release and a tag for said update, and draft it to the github repo.
This means I no longer have to manage builds myself, which sometimes took several hours to fix environment issues and more.
It also means that whenever I push an update, the app automatically reflects said update in an appropriate branch (we don’t like testing in production, right?).