You can't log out of U1 because you are never logged in. What U1 does is allow this specific device access to your account, which is why what you can do is "remove the device".
Now, why not rename that button to "log out" and put it in the account tab? Well, technically it's easy to do. But!
If you logout, you may later log back in. And if you log in with a different account, what should we do?
Currently, we give a cryptic error (ROOT_MISMATCH) which is not a very good idea, and we *could* remove that error, But!
Remember we are a file sync app. Presumably the user has files that he has synced with U1. So if he logins with another user, he's going to sync all those files to the new account and download the new account's files. Those files will become hopelessly mingled and/or overwritten.
So, that's not something we want to happen, either.
Therefore, what can we do? And here I punt it to design for thought and discussion ;-)
And now the long version.
You can't log out of U1 because you are never logged in. What U1 does is allow this specific device access to your account, which is why what you can do is "remove the device".
Now, why not rename that button to "log out" and put it in the account tab? Well, technically it's easy to do. But!
If you logout, you may later log back in. And if you log in with a different account, what should we do?
Currently, we give a cryptic error (ROOT_MISMATCH) which is not a very good idea, and we *could* remove that error, But!
Remember we are a file sync app. Presumably the user has files that he has synced with U1. So if he logins with another user, he's going to sync all those files to the new account and download the new account's files. Those files will become hopelessly mingled and/or overwritten.
So, that's not something we want to happen, either.
Therefore, what can we do? And here I punt it to design for thought and discussion ;-)