They need not be at odds. If one customer is asking for it, it's worth taking a step back to see how you might implement both the fulfillment of their request as well as the groundwork for a larger product feature (set). This is why I recommend sending user feedback directly to product backlog (refined through ongoing dialog with the user submitting it as needed).
This is similar to the "step back and look for common threads" approach I recommend to those with multiple product ideas instead of following the (usually VC-driven) mindset of focusing on one thing and dropping everything else. If there's enough overlap, working on or even just planning one product may improve another.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
They need not be at odds. If one customer is asking for it, it's worth taking a step back to see how you might implement both the fulfillment of their request as well as the groundwork for a larger product feature (set). This is why I recommend sending user feedback directly to product backlog (refined through ongoing dialog with the user submitting it as needed).
This is similar to the "step back and look for common threads" approach I recommend to those with multiple product ideas instead of following the (usually VC-driven) mindset of focusing on one thing and dropping everything else. If there's enough overlap, working on or even just planning one product may improve another.