justdave
commented
11 years ago I would recommend any authentication failure cause an exception to be thrown, which is trapped and shown to the user (perhaps as a notification?).
Making a test connection to test the account when it's entered in the setup would probably be useful, too.
When you add a new account in the account setup, there is no feedback to tell you if you got your password correct or not.
I screwed mine up the first time and wound up getting my account locked out because it didn't tell me I screwed up and then proceeded to make 6 attempts to log in to generate the dashboard (it only takes 5 failures to get locked out). None of those attempts caused any kind of error visible to the user (only in the logcat output), and the dashboard simply failed to populate.