Customer App: Restaurant Review Display & Multiple Review Bug

Hey guys! Today we're diving deep into a couple of major issues found within the customer app of our multi-vendor food delivery system, specifically focusing on restaurant reviews. It's super important that these reviews are displayed correctly and that the system prevents duplicate submissions to maintain the integrity of the feedback. So, let's break down the bug, how to reproduce it, what we expect to happen, and the juicy details.

The Bug: Reviews Not Updating on Discovery Screen & Multiple Reviews Allowed

The core problem here is twofold. First, when a customer leaves a review for a restaurant through their order history, that review doesn't immediately reflect on the restaurant's listing in the discovery screen. This is a big deal because those initial impressions are super crucial for attracting customers. Imagine browsing for food and seeing outdated reviews – that wouldn't be very helpful, right? The review should be visible on the discovery screen.

Second, and equally important, the app is currently allowing customers to submit multiple reviews for the same order. This can lead to skewed ratings and potentially game the system. We want genuine feedback, and allowing multiple reviews opens the door to abuse. We need to ensure that a customer can only review an order once. This is crucial for maintaining the fairness and accuracy of our review system, ensuring that the feedback reflects a single, considered opinion per transaction. This not only protects the integrity of the ratings but also builds trust among users, who rely on these reviews to make informed decisions.

These issues impact the user experience significantly. Customers rely on up-to-date reviews to make informed decisions about where to order food. When reviews don't display correctly or are potentially inflated due to multiple submissions, it erodes trust in the system. This can lead to decreased customer satisfaction and ultimately affect the success of the multi-vendor food delivery app. It is essential that we address these bugs promptly to maintain the integrity of our platform and ensure a positive experience for all users.

Steps to Reproduce: Let's Get Bug Hunting!

Okay, so how can we actually see this bug in action? Follow these steps, and you'll be a bug-squashing pro in no time:

1. Head to the Customer Application: Fire up the customer app – this is where the magic (or, in this case, the bug) happens.
2. Navigate to Profile: Look for the Profile menu button. It's usually in the bottom navigation or tucked away in a menu.
3. Order History: Under "My Orders," find and click on "Order History." We're going to be playing with past orders.
4. Past Orders: Select the "Past" tab to view your completed orders. This is where you'll find the orders you can review.
5. Leave a Review: Pick any past order and leave a review. Rate the restaurant, add some comments – go all out!
6. Discovery Screen Check: Now, this is the crucial part. Go back to the discovery page (where you browse restaurants). Find the restaurant you just reviewed. The review should be visible on the discovery screen.
7. Observe the Issue: You'll likely notice that the review you just submitted isn't immediately reflected on the restaurant's listing. It might only update when you actually tap into the restaurant's detailed view. This is the first part of the bug!
8. Multiple Reviews: Try reviewing the same order again. You should be able to submit another review, which highlights the second part of the bug.

By following these steps, you can consistently reproduce the bug and see the issue firsthand. This makes it much easier to understand the problem and verify the fix once it's implemented.

Expected Behavior: How It Should Work

Alright, so we know what's happening wrong. Let's talk about how it should work. This is crucial for understanding the desired outcome and ensuring that the fix actually solves the problem.

• Immediate Review Display: When a customer submits a review for a restaurant, it should be displayed immediately on the restaurant's listing in the discovery page. No tapping into the restaurant details required! This ensures that potential customers see the most up-to-date feedback when making their choices. It creates a seamless and responsive experience, building trust and transparency within the app. The idea is that the review should be visible on the discovery screen as soon as it is submitted, without the need for any further action from the user.
• One Review Per Order: A customer should only be allowed to review an order once. This prevents duplicate submissions and ensures that the ratings accurately reflect the consensus of unique customer experiences. We need to implement a mechanism that prevents multiple reviews for the same order, safeguarding the integrity of the review system. Allowing only one review per order maintains fairness and prevents potential manipulation of ratings, which is crucial for the reliability of the app's review system.

These two points are key to a well-functioning review system. Immediate display provides timely feedback, and limiting reviews to one per order ensures accuracy and fairness. By achieving these behaviors, we can create a more reliable and trustworthy platform for both customers and restaurants.

Additional Information: The Technical Stuff

To give you the full picture, here's some additional information about the environment where this bug is occurring:

• Device: We've seen this issue reported on an Infinix Hot 50, but it's likely not limited to this specific device. It's essential to test across a range of devices to ensure the fix is comprehensive.
• OS: The operating system is not specified in the original bug report. Further investigation may be needed to determine if this bug is OS-specific.
• Browser: The report mentions "Application," so we're dealing with a native mobile app, not a web browser.
• Version: The application version is 14. This helps us pinpoint when the bug was introduced and track down potential code changes that might have caused it. Knowing the version number is crucial for developers to trace the origin of the bug and implement a targeted fix.

We also have a screen recording (WhatsApp.Video.2025-01-15.at.11.49.12.AM.1.mp4) that visually demonstrates the bug. This is super helpful for developers to see the issue in action and understand the user's experience.

Conclusion: Let's Fix This!

So, there you have it! We've identified a critical bug in the customer app that affects how restaurant reviews are displayed and submitted. By understanding the bug, how to reproduce it, and the expected behavior, we're well-equipped to tackle this issue head-on.

The next steps involve the development team digging into the code, identifying the root cause of the problem, and implementing a fix. Once the fix is in place, rigorous testing will be crucial to ensure that the bug is truly squashed and doesn't resurface in the future. This includes testing across different devices and operating systems to ensure a consistent user experience for all customers.

Remember, a reliable review system is essential for building trust and transparency within our food delivery platform. By addressing this bug promptly and effectively, we can ensure that customers have access to accurate and up-to-date information, leading to better ordering decisions and a more positive experience overall. Let's make it happen, guys!