nigelheng / pe

0 stars 0 forks source link

Add-on to problem of not allowing repeated date itineraries #8

Open nigelheng opened 4 months ago

nigelheng commented 4 months ago

image.png

The history becomes way too full. There should be a way to clear the history which will allow dates in the repeat locations again. Also the history should be able to be sorted either by location, price or other attributes used in the program so that it is readable.

soc-se-bot commented 4 months ago

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

Thank you for raising these issues up! To address these issues:

  1. Issue 1: "There should be a way to clear history which will allow dates in the repeat locations again" While our team agrees that some couples would be interested in visiting repeat locations again, this goes against the value proposition of our product, stated within the Developer Guide

Screenshot 2024-04-22 121017.png

Our value proposition promises 'new and interesting date ideas', and for our team, that implies that every activity/restaurant generated must not be a repeat of previous date ideas. The aim of Flirt & Fork is to inspire new ideas/places that couples may not normally know about, and we believe that recommending couples to revisit past experiences does not achieve this objective.

  1. Issue 2: The history becomes way too full Once again, while we acknowledge that after multiple dates, the 'history' list will become quite long, we reiterate it back to our value proposition. Maintaining a history database of all past dates is necessary to ensure that all future ideas/itineraries mentioned remains new and fresh. Morever, we highlighted the purpose of the History Tracking feature below, which is to allow users to track their date history and preferences. We believe this would not be possible if we allow users to clear their history, as it will result in an incomplete history database

Screenshot 2024-04-22 121924.png

  1. Issue 3: the history should be able to be sorted either by location, price or other attributes used in the program so that it is readable While we appreciate the feedback and suggestions, our team believes that the functionality we have achieved within this period is sufficient for our current working product. Given the tight timeline, we believe that our current product is able to deliver on our value proposition. Hence, we feel that it is not a bug as stated below (retrieved from [https://nus-cs2113-ay2324s2.github.io/website/admin/tp-pe.html#pe-phase-2-developer-response])

Screenshot 2024-04-22 122345.png

We appreciate the feeback though, and we will consider enhancing this current feature moving forward!

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: [replace this with your reason]