I know this topic has been revised → I just have a more specific situation to which it relates, and I would like to choose your brain.
I am writing an application that asks for the user name at the first boot. This username is sent to my server, checked for uniqueness and entered into the database along with the UUID generated by mysql. This username is also used to create a virtual directory for the user, so user "evan" gets blabla.com/evan. The UUID is sent back to the phone, where it is stored locally (not yet set to the storage type, sqlite is currently used).
The application never asks for a password. The phone saves the UUID generated by my server and sends this identifier along with the saved username after boot to identify the user. I like the idea of not using passwords, because passwords simply open too many Pandora's mailboxes and regardless of the fact that I am Greek American, I would prefer to avoid Pandora.
I like this approach because if a user ever factory drops his phone and transmits it, the next person will not be registered in the old person's account. I don't like this approach because I'm worried about how many URLs will be dead, as people delete data from their phone and create new accounts (for some reason they will do this, I'm not sure).
I really want to avoid the need to contact customers who want to return their URL. What an intern who could better spend on my coffee.
My stubborn brother complains that the accounts will not be transferred from one device to another: "What if I buy a new phone and want my old account and URL?"
, " ", , URL- X . " " , URL. " ", , , , , .
, - , . - , , URL- ( , ).
, , . // .
, .
-Evan