Auth is low priority and should be implemented only when the core functionality is done. However, thinking about it in the current stage is not a bad idea.
For the scope of the app, it requires a very minimal amount of Authentication and almost no Authorization. User data is just another way to say cloud-saved reader configs and maybe bookmarks or notes in the future.
Some options to consider:
Roll your own (with libraries or something like Authorizer). Yes I remember the old adage, but for this app I think it's simple enough for this to be justified.
Use an identity manager like Zitadel (pretty overkill)
I guess a better direction to take is to start with Pocketbase first and think about implementing auth later.
It shouldn't be hard to migrate, our entire database is basically just 2 files anyways.
Auth is low priority and should be implemented only when the core functionality is done. However, thinking about it in the current stage is not a bad idea. For the scope of the app, it requires a very minimal amount of Authentication and almost no Authorization. User data is just another way to say cloud-saved reader configs and maybe bookmarks or notes in the future.
Some options to consider: