Open DDzuikeai opened 4 years ago
Thanks for your feedback.
Our program is intended to be case-sensitive in taking in names. We intended for the names to be stored, and displayed in the contact list as how the user types it in, just like how we store contact names in our phone's contacts.
Thank you.
Team chose [response.Rejected
]
Reason for disagreement: This is actually different with our phone's contacts. Because in our phone, we can also see other information of a contact person (phone number, address...) which can help us identify the person. But in your app, information related to a certain person is just his timetable. We can't really identify who is who based on that. This design could actually bring much inconvenience in the coming two senarios.
John
s, and he isn't so careful about the uppercase and lowercase. In his contact lists, there could exist several John
s(John, JOHN, john), and he already forgot who is who. In this case, it's better to prevent the user from adding a new John
if the name is already used.John
, but also not so careful about the uppercase and lowercase. He already added John
in his contact lists, but forgot that. And a few days later he added John
again in a different format. So there could be several John
s in his lists while he just wanted one.Team chose [severity.VeryLow
]
Originally [severity.Medium
]
Reason for disagreement: The two senarios above can really bring inconvenience to the user. Personally, I care about this issue very much. But I do understand people can have different attitudes towards it. But in all, I think the severity shouldn't be lower than severity.Low
,
The user name is case sensitive. Which I think is unreasonable.
In this picture I actually have three profile with the same name, but JOHN and John is exactly the same person. If the app is case sensitive, may lead to much inconvenience.