AwesomeApp is an application created by students for students! The application is intended only for Udacity students - Google Developer Challenge scholarship 2017/2018 European edition Thanks to this application, students who work on the same project will be able to contact other using Slack and solve problems together.
when the user just installed the applications and quickly pressed the button with one of the paths, and the data has not yet downloaded, he sees only a blank screen without a message - add a message and allow the screen to refresh - SwipyRefreshLayout
when a new user registers, he should have empty fields and not filled with data from the first position of tables - can we add empty strings as the first position of each table in the database?
These fields are empty even after filling out the profile and saving to the database.
They are not very necessary because they are stored in the user's panel - the only advantage of saving them to the database is that it is easier to identify the user manually from the database panel - we can opt out of saving this data
if we leave it in this way, the query to the database will download all users who are currently working on a given project at once. No problem when there will be 20 but what if there are 500 of them?
Loading a new chunk of data should depend on the recyclerView scroll position - now it is done with the button and stops working if there is no data loaded in the layout - the problem will be solved if the loading depends on the recyclerView
If we do not save the user in the database - he has no values assigned - language_1, language_2, track ... and so on. As a result, the function updating the user's data does not find it, and his data does not appear immediately in the list.
Another problem is when the user already has an account, but he will log out of it and want to create a new one - when the screen with user data appears, his last data is loaded (from the previous account from which he logged out)
the first login calls the saveUser function, which after saving the data switches the form to MainActivity - this should not happen the first time the user logs in
When the user gets impatient and goes back to main activity before the data is saved - saveUser function works in the background and again intent to MainActivity when will be complete. This will happen only when the user has a poor connection to the internet - or when it's the first entry in the database of this user (I do not know why it's slower then)
Feed all the project info correctly.
The document name is _Px with x the project number : for example ABND_P1
Each project has these fields :
If more informations is needed, write a comment here