When the user is not logged in, the app shows the authentication activity. If the user presses the login button, the pre-built firebase UI pops up in order for the user to authenticate. Once the user is indeed authenticated, the list item activity is shown. If the authentication somehow fails, an error message will show up and indicate to the user that authentication has failed. Inside the latter activity, a log out button is shown to the user in for her/him to log out. Pressing the button effectively logs out the user and shows the authentication activity again. Finally, if the user is logged in, stops/exists/restarts the app, its authentication is effectively persistent.
A few things to point out :
The logout button has been added to the list item activity without much thinking. I don't think it will stay there for a long time. to be refactored / placed someshere else later.
The authentication activity is somewhat stark and very simple.
The authentication persists but not infinitely over time. We should handle the case when an authentication token expires.
Addresses issues #30, #31, #28 and #17.
When the user is not logged in, the app shows the authentication activity. If the user presses the login button, the pre-built firebase UI pops up in order for the user to authenticate. Once the user is indeed authenticated, the list item activity is shown. If the authentication somehow fails, an error message will show up and indicate to the user that authentication has failed. Inside the latter activity, a log out button is shown to the user in for her/him to log out. Pressing the button effectively logs out the user and shows the authentication activity again. Finally, if the user is logged in, stops/exists/restarts the app, its authentication is effectively persistent.
A few things to point out :