deniskrr / conferencer Goto Github PK

Create the Login Activity (only the GUI). The naming convention for UI controls' id is: "controlType_whatFor_where" or "controlType_where" if it is self-explanatory. Example: "edittext_username_register", "button_register".

Make it look similar to RegisterActivity (check the XML for style attribute) but use only one EditText for both Username and Email as the user should be able to log in using either one.

Reference: https://developer.android.com/training/constraint-layout

Add functionality to LoginActivity, after @ColdCipri creates it.

The user should be able to log in using the username or the email.

If the text entered by the user is not a username in the database, treat it as an email address. If the text is a username, extract the email associated with it from the database.

Use signInWithEmailAndPassword method to log the user in.

Display a Toast with the log in result.

Database structure:

Reference:
https://firebase.google.com/docs/auth/android/password-auth
https://firebase.google.com/docs/firestore/query-data/get-data

Create a Class Diagram in StarUML.

Use the diagrams branch.

You will have to update this as we add new classes to the application.

Reference:
https://youtu.be/UI6lqHOVHic

BUT PLS WATCH TUTORIALS FIR$$7

BUT PLS WATCH TUTORIALS FIR$$7

Create an ER Diagram in StarUML. (File - New From Template - Data Model)

Use the diagrams branch.

Read the project requirements and extract the basic entities (such as User, Conference) and add relations between them. We will add more specific entities and fields as the project progresses.

Reference:
http://www.cs.uregina.ca/Links/class-info/215/erd/#ent