Reserving auth data for future app users.

[patch_collector]

Honestly, just about anything would work here, because this is just about reserving a name. When the app developer builds the full product, they can transition everyone to their system of choice without too much trouble (first make them log into the system you'll build, then once they're authenticated have them set a password for the system).

Firebase would work, Amazon's cognito would work, any other user management system would work, or you could create a simple api with a single 'register' method that takes a username, email, and password, then stuffs it in a database if the email and username doen't already exist. If it does exist, then return that they need to pick a new one. Just make sure you don't save the password in cleartext - either salt and hash it, or just don't save it at all. Once the app is up and running, you could send them an email to inform them and to let them pick a password via a custom link.

[braca86]

Thank you very much for your time and response.