search

saajidshaik02 / pe

0 stars 0 forks source link

[UG] App's funcitionality as a whole #5

Open saajidshaik02 opened 1 week ago

saajidshaik02 commented 1 week ago

To me, as I was viewing the whole app, it felt very similar to AB3. Just wanted to point it out based on the below 3 screenshots.

  1. Basically the same features as AB3, except changing the input tailored to student details

  2. UI interface is the same, even the icon, background, layout seem almost similar.

I get it, its a contact application so its going to be very similar.

My suggestion is perhaps, you could have explored into tracking details of these students in the CCA. For example, which dates they came training, their time in vs time out. Or like their experience level and etc etc details. There is much room for features, not indicated in Future enhancements in DG

Alternatively, if you feel that the above suggestion changes what you want out of this AB3 contact app, perhaps can work on UI details. For example, since its tailored to students, the UI could have been more fun and visually appealing.

image.png

image.png

image.png

nus-pe-bot commented 1 week ago

Team's Response

Thank you for providing us with suggestions for our address book. However, we added a Pagination as well as Status Bar Footer changes to our Ui, displaying 10 contacts per page so as to reduce the amount of scrolling the user has to do and also showing them how many contacts are displayed at any one time.

While we do agree that our product is very similar to AB3, we did mention that in Appendix: Effort, most of us did struggle a lot with this project as it was very unfamiliar to many of us not CS first majors. Hence, at the start, we provided a scope that was very in line with our competence levels, which we could achieve during the given time period. Which is why we were amazed at the various other projects that were created, having so many different features in such a short amount of time. So yes, apologies for disappointing you with our seemingly lack of effort but we did learn a lot from this product and module as a whole.

However, I’m not sure if DocumentationBug is relevant to this issue, it seems less of a bug and more as a “Recommended Things to Add if we were to Continue this Project”. Hence we put it as a Feature Flaw

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: [replace this with your explanation]

## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.DocumentationBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]