Account Settings

Objective

Define the minimum requirements for the flow related to accessing, viewing, and editing the vendor user's account information, including personal data, password, and general preferences. The flow must ensure security, clarity, and usability in managing account settings.

Insights

• The settings screen must be responsive and adaptable to various screen sizes.

• The email field must reject invalid or duplicate addresses already in the system.

• Critical changes (e.g., password or email) should be auditable and optionally notified via email.

---

Accessing the User Area

01 - “User” icon in bottom navigation

Must be visible and accessible from all main screens. Tapping it must lead to the account settings screen.

Mandatory:

Access to account settings must be available at all times without requiring multiple steps.

Recommended:

Display the user’s name and profile picture in the navigation when logged in.

---

Account Settings Screen

02 - “Edit Profile” section

Must be located at the top of the settings screen with clear icon and label.

03 - “Logout” option

Must be positioned safely (at the bottom of the screen) and require confirmation before logging out.

Mandatory:

Logging out must terminate all active sessions.

Recommended:

Include a “Preferences” section for visual and notification customizations.

---

Profile Edit Screen

04 - Editable fields (name, email, password)

Must allow free editing, include password visibility toggle, and validate email format. Password must be entered twice for confirmation.

05 - “Save changes” button

Must remain disabled until at least one field is changed and all required fields are correctly filled.

Mandatory:

Passwords must meet a minimum policy (e.g., 8 characters, symbol, number).

Recommended:

Display a confirmation alert and success feedback after saving changes.

---

Mandatory Messages

• When passwords do not match:

  Passwords do not match. Please check and try again.

• When changes are saved successfully:

  Changes saved successfully.

Expected Behaviors

• Data editing must be protected by a valid user session.

• Password fields must allow optional visibility via eye icon.

• The logout button must force token expiration and redirect to the login screen.

• All input fields must be compatible with screen reader accessibility.