Restaurant Review Bug: Updates Not Showing On Discovery Screen
Hey guys! We've got a bit of a situation with our restaurant app, specifically how customer reviews are displayed. Let's dive into the issue, how to reproduce it, what we expect to happen, and the nitty-gritty details.
Describe the Bug
Okay, so here's the deal. When a customer leaves a review for a restaurant after placing an order, that review should show up on the restaurant's listing in the discovery screen, right? That way, other users can see the latest feedback and make informed decisions. But, that's not what's happening right now. The review isn't updating on the discovery screen immediately. It seems like you have to actually go into the restaurant's page to see the new review, which isn't ideal.
This is super important because real-time updates are key to a smooth user experience. Imagine a customer leaving a glowing review after a fantastic meal – we want that positive feedback to be visible right away! Conversely, if there's constructive criticism, other users should be aware of it. Delaying the display of reviews can lead to users missing out on crucial information, potentially impacting their dining choices.
Another big thing: customers should only be able to review an order once. We don't want folks accidentally submitting multiple reviews for the same experience. This can skew the overall rating and make it difficult for both the restaurant and other users to get an accurate picture. Think about it – if someone had a particularly strong feeling about their order (good or bad), they might be tempted to submit multiple reviews if the system allowed it. This could unfairly inflate or deflate the restaurant's rating. Ensuring a one-review-per-order policy keeps things fair and balanced.
So, in a nutshell, the bug has two parts: review updates aren't showing on the discovery screen in real-time, and there's no mechanism to prevent multiple reviews for the same order. Both of these issues need to be addressed to ensure a reliable and user-friendly review system.
Steps to Reproduce
Alright, wanna see this bug in action? Here's how you can reproduce it:
- Head to the Customer Application: Fire up the customer app, guys.
- Go to Your Profile: Tap on that profile menu button – you know the one.
- Dive into Order History: Look for "Order History" under "My Orders" and select "Past". This is where all your previous orders live.
- Leave a Review: Pick any past order and leave a review. Rate the experience, write a comment – the whole shebang.
- Return to the Discovery Screen: Now, this is where the magic (or rather, the bug) happens. Go back to the discovery page – the main screen where you browse restaurants.
- Check the Restaurant: Find the restaurant you just reviewed. You'll notice the review isn't updated until you actually tap into the restaurant's details page. That's the problem!
Let's break down why these steps are so effective at showcasing the issue. First, by navigating through the order history and selecting a past order, we're simulating a real-world scenario where a customer wants to provide feedback after their dining experience. The act of leaving a review, including rating and comments, mimics a typical user interaction. The crucial step is then returning to the discovery page. This is where we expect to see the immediate reflection of the newly submitted review. However, the bug prevents this real-time update, forcing the user to delve deeper into the restaurant's details to view the changes. This extra step disrupts the user flow and highlights the discrepancy between the expected behavior (instant update) and the actual behavior (delayed update).
By consistently following these steps, anyone can easily replicate the bug and understand the frustration it causes for users. This clarity is essential for developers to accurately diagnose and address the problem.
Expected Behavior
Okay, so what should happen? It's pretty straightforward:
- Immediate Updates: When a customer submits a review, it should immediately show up on the restaurant's listing on the discovery page. No tapping required!
- One Review Per Order: The app should only allow one review per order. Once a customer has reviewed an order, the option to review it again should be disabled or removed.
Let's dig a little deeper into why these expectations are so crucial for a positive user experience. For the immediate updates, think about the real-time nature of the online world. We're used to instant feedback and information. When a customer takes the time to leave a review, they expect their feedback to be visible and impactful. A delay in updating the discovery screen creates a disconnect and can even make the user wonder if their review was submitted successfully. Imagine the customer's thought process: "Did my review even go through? Why isn't it showing up?" This uncertainty can lead to frustration and a feeling that the app isn't working as it should.
On the other hand, limiting reviews to one per order is all about maintaining fairness and accuracy. As we discussed earlier, multiple reviews from the same person can skew the overall rating. By enforcing a one-review policy, we ensure that each customer's voice is heard, but not amplified disproportionately. This creates a more balanced and reliable representation of the restaurant's performance. It's also important to consider the restaurant's perspective. They rely on genuine feedback to improve their services, and a flood of multiple reviews from the same person can be misleading and unhelpful.
In essence, the expected behavior is about creating a transparent, fair, and user-friendly review system that benefits both customers and restaurants. By implementing these two key features – immediate updates and a one-review-per-order limit – we can achieve a more trustworthy and engaging platform.
Additional Information
We've also got a screen recording that shows the bug in action. Check out WhatsApp.Video.2025-01-15.at.11.49.12.AM.1.mp4 to see it for yourself.
Device Information
- Device: Infinix Hot 50 (Example)
- OS: Windows (Example - though this is likely an Android device based on the name)
- Browser: Application
- Version: 14 (Example)
It's important to include detailed device information when reporting a bug. This helps the development team understand if the issue is specific to certain devices, operating systems, or app versions. The device model (e.g., Infinix Hot 50) provides information about the hardware and software configuration. The operating system (e.g., Windows – although likely Android in this case) indicates the underlying platform on which the app is running. The browser (in this case, “Application” since it's a native app) clarifies the environment in which the bug is occurring. Finally, the app version (e.g., 14) helps pinpoint if the issue was introduced in a recent update or has been present in previous versions.
By providing these details, we're giving the developers a clearer picture of the bug's context. This can significantly speed up the debugging process and ensure that the fix is effective for all users. Think of it like providing a detailed description of a medical symptom to a doctor – the more information they have, the better they can diagnose the problem and prescribe the right treatment.
So, there you have it! That’s the scoop on the restaurant review bug. Let's get this fixed so our users can have the best experience possible!