Justification for severity label: The inability to leave certain fields, such as address, as optional can lead to significant inconvenience for users. In real-world scenarios, users may not always have access to complete information about a contact. For instance, some parents might only want to disclose phone number but not email address, and vice versa.
Forcing users to input such details, even when they are unnecessary, creates a poor user experience. It may discourage users from adding contacts on the spot, especially in situations where only essential information like name and phone number is known. This restriction also reduces the flexibility of the application and fails to accommodate realistic user needs, where incomplete data entry is common and sometimes intentional.
In severe cases, users may have to resort to inputting inaccurate information just to bypass the system constraints, which undermines data integrity.
Allowing optional fields is a common usability standard in contact management systems, and the lack of it here creates friction and prevents the application from being truly user-friendly or practical in everyday use.
Justification for severity label: The inability to leave certain fields, such as address, as optional can lead to significant inconvenience for users. In real-world scenarios, users may not always have access to complete information about a contact. For instance, some parents might only want to disclose phone number but not email address, and vice versa.
Forcing users to input such details, even when they are unnecessary, creates a poor user experience. It may discourage users from adding contacts on the spot, especially in situations where only essential information like name and phone number is known. This restriction also reduces the flexibility of the application and fails to accommodate realistic user needs, where incomplete data entry is common and sometimes intentional.
In severe cases, users may have to resort to inputting inaccurate information just to bypass the system constraints, which undermines data integrity.
Allowing optional fields is a common usability standard in contact management systems, and the lack of it here creates friction and prevents the application from being truly user-friendly or practical in everyday use.