8. Sign In / Sign Up Screens #82
Labels
architecture
Move to clean architecture
feature
New feature or request
sign in / sign up
Sign In / Sign up functionality
Milestone
8.1. Sign in using email use-case: User enters email and password. The credentials are checked on the server (call to server API). If login was successful then user is redirected to home screen. If an error appeared then user sees error message.
8.2. Sign up using google account use-case: User clicks google icon, user google account credentials are checked. Successful result creates an account for the user locally and makes an API call to the server to add new account. User gets redirected to the home screen.
8.3. Sign up using Facebook account use-case: User clicks Facebook icon, user Facebook account credentials are checked. Successful result creates an account for the user locally and makes an API call to the server to add new account. User gets redirected to the home screen.
8.4. Send password reminder use-case: User enters email on the Forgot Password Screen and clicks “Send” button”. A Server API call is made to check if use exists and to send forgot password email. If it is successful user is sees message from the server (like “An email with password reminder was sent to [email protected]”). If an error appears user see that error.
8.5. Sign up use-case: User fills in the fields on the Sign Up Screen and clicks “Sign Up” button. API request is made to create new user account. If successful then local record for that user is created and user is redirected to home screen. If an error appears then user sees it on the Sign Up Screen.
E-commerce App Use-Case Description
Within this task you need to do the following:
Pull all data from local database and render it on the screen.
At this time mock remote repository calls for fetching data from a local JSON file. The data structure and method names should be taken from WooCommerce REST API docs.
The text was updated successfully, but these errors were encountered: