Or you can do as I do and synchronize settings yourself through Dropbox or a billion other ways.
I remember the good old days when software companies used to like to reuse stuff to prevent having to use user data. I used YNAB and they had all the user data in a Dropbox folder. So their app knew who you are and I/O’d to Dropbox, but the YNAB company didn’t know.
Then they switched from software to service and all of a sudden it was essential that they know their customer and have an account and whatnot.
Proper software design minimizes complexity. [0] If users are likely to already have a common, free way to synchronize settings, design for that. Don’t add another risk by collecting PII. Especially if it makes you money in ways you aren’t disclosing.
I remember the good old days when software companies used to like to reuse stuff to prevent having to use user data. I used YNAB and they had all the user data in a Dropbox folder. So their app knew who you are and I/O’d to Dropbox, but the YNAB company didn’t know.
Then they switched from software to service and all of a sudden it was essential that they know their customer and have an account and whatnot.
Proper software design minimizes complexity. [0] If users are likely to already have a common, free way to synchronize settings, design for that. Don’t add another risk by collecting PII. Especially if it makes you money in ways you aren’t disclosing.
[0] Steve McConnell Code Complete, page 80 - http://aroma.vn/web/wp-content/uploads/2016/11/code-complete...