search

avellinwong01 / pe

0 stars 0 forks source link

UG: Add scheduled workout with activity breakdown is too complicated #17

Open avellinwong01 opened 2 years ago

avellinwong01 commented 2 years ago

image.png

Details here are too complicated, again the user will probably find out from using the app itself when he/she types in a wrong format (with suitable error messages thrown). The command itself is also too complicated for fast-typists with too many things to watch out for

nus-pe-script commented 2 years ago

Team's Response

User guide has comprehensive behavior as well as it is not definite that the user uses the app BEFORE reading the UG as it may very well be the other way around. Basically it could be either way around as such it was chosen to have more extensive documentation, due to its more greater complexity.

The activity breakdown is OPTIONAL and for individuals that want a more activity breakdown. The user reap more benefits in terms of having a comprehensive workout breakdown in your schedule by having the activity breakdown IF they are willing to spend more time.

image.png

Also using the up arrow key can return the invalid command and users can just adjust adjust the previous commands based on the error message. Since it is a more complicated "advanced" feature, users will naturally have to get used to it and there are bound to be errors when first starting out using the feature.

I do not see an issue with the command for fast-typists, you could argue that you have to type 2 commands worth of characters but once again you also get the extra benefits of a detailed activity breakdown for your workout which is beneficial for more dedicated individuals scheduling workouts. Once again, users are not forced to use this optional feature.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: Even though this is an optional feature, the number of parameters and associated limitations necessary (I can't remember if your app was able to handle all the limitations that is written in the UG about swapping of prefixes and duplicates) still does not seem to me to be suitable for fast typists. Though I suppose as this is an optional feature the inconvenience posed to users will be rare.

:question: Issue severity

Team chose [severity.Low] Originally [severity.High]

Reason for disagreement: [replace this with your explanation]