Enatega App: Filters Not Applying On Restaurant Page (Android)

by Admin 63 views
Enatega App: Filters Not Applying on Restaurant Page (Android)

Hey guys! Let's dive into a pesky bug reported in the Enatega Customer Application for Android. Users are experiencing issues with the filter functionality on the restaurant page. It seems filters aren't being applied correctly, which can be super frustrating when you're trying to narrow down your food choices. This article will break down the bug, how to reproduce it, the expected behavior, and all the technical details.

Bug Description

The core problem is that the filters are not working as they should on the Restaurant Page within the Enatega Customer Application for Android. Even after a user meticulously selects specific filter options – let's say they're craving Italian and only want to see restaurants with a 4-star rating – the restaurant list doesn't dynamically update to reflect those choices. It's like the app is ignoring your preferences, which isn't ideal when you're hungry and time is of the essence.

This malfunction directly impacts the user experience. Imagine you're in the mood for a specific cuisine or have dietary restrictions. Without functional filters, you're stuck scrolling through an endless list of restaurants, many of which won't meet your needs. It's a significant hurdle in an app designed for convenience and efficiency. The inability to effectively filter restaurants turns a simple task into a time-consuming ordeal, potentially driving users away from the application.

The issue also compromises the app's competitive edge. In today's crowded food delivery market, users expect a seamless and personalized experience. Features like filtering are crucial for helping users quickly find what they want. When these features fail, the app loses its appeal, and users are more likely to switch to a competitor offering a smoother experience. It's not just about fixing a bug; it's about maintaining user satisfaction and staying competitive in the market.

Steps to Reproduce

So, how can we make this bug happen ourselves? Here's a step-by-step guide to reproduce the issue:

  1. Open the Enatega Customer Application on your Android device. This is your starting point, just like any other app interaction.
  2. Tap on the 'Restaurants' menu button. This action takes you to the main screen where restaurants are listed, which is where the filtering issue surfaces.
  3. Look at the top right corner and click on the 'Filters' button. This should reveal all the available filter options, such as cuisine types, ratings, price ranges, and so on.
  4. Now, here's the crucial part: select any filter – maybe you want to see only vegan options, or perhaps you're on a budget and need something under $20. Apply your selection.
  5. Observe the results. This is where you'll see the error in action. The restaurant list should update to reflect your filter choices, but it doesn't. The list remains unchanged, showing all restaurants regardless of your selections. It's like the app isn't listening to your instructions.

By following these steps, you can consistently reproduce the bug and confirm that the filters are indeed not working as expected. This consistent reproduction is vital for developers, as it helps them pinpoint the exact location and cause of the problem. The clearer the steps to reproduce, the easier it is for developers to replicate the issue and implement a fix.

Expected Behavior

Let's talk about what should happen when those filters are applied. The selected filters should dynamically modify the restaurant list. This means that as soon as you choose your filters (Cuisine, Rating, Price Range, etc.), the list of restaurants should instantly update. Only those restaurants that perfectly match your chosen criteria should remain visible. It's all about creating a tailored experience, so you're not sifting through irrelevant options.

Imagine you've selected "Italian" cuisine and a minimum rating of 4 stars. The restaurant list should, without delay, narrow down to show you only Italian restaurants with a 4-star rating or higher. This immediate feedback is key to user satisfaction. It confirms that the app is responding to your input and working efficiently. Waiting for a manual refresh or a delayed update breaks the flow and creates a clunky user experience.

Once a filter is applied, it should remain active until you manually clear it. This persistence is crucial for maintaining a consistent experience. Let’s say you've set your filter to "Open Now" because you're ready to order. If you navigate away from the restaurant list – perhaps to check your profile or browse saved addresses – the "Open Now" filter should still be in effect when you return. You shouldn't have to reapply it every time you switch screens. This persistence ensures that your preferences are respected throughout your session, making the app more user-friendly and intuitive.

Technical Details

Here’s the technical lowdown based on the bug report:

  • Device: The issue was reported on an Infinix Hot 50, but it’s possible it affects other Android devices as well.
  • OS: The device was running on Android, version 14.
  • App Version: While the specific app version isn’t mentioned, it’s crucial to know this for debugging. (Tip: When reporting bugs, always include the app version!)
  • Observed Behavior: The video recording (az_recorder_20250108_110415.mp4) clearly shows the filters not working. This visual evidence is super helpful for developers.

Potential Causes and Solutions

So, what could be causing this filter fiasco? Here are a few potential culprits:

  1. Backend API Issues: The app might not be correctly communicating with the backend server to fetch filtered results. There could be a problem with the API endpoint that handles filtering, or the app might be sending the filter parameters incorrectly.
  2. Frontend Filtering Logic: The filtering logic within the app itself might be flawed. The app might be receiving the correct data from the backend but failing to apply the filters properly on the frontend.
  3. Data Handling: There could be issues with how the app is storing and managing the restaurant data. If the data is not structured correctly, it can be difficult to filter efficiently.
  4. Caching Problems: The app might be caching restaurant data and not updating it when filters are applied. This could lead to the app displaying outdated results.
  5. UI/UX Bugs: In some cases, the problem might not be with the filtering logic itself, but with the user interface. The filter options might not be correctly linked to the filtering functions, or there might be visual glitches that make it seem like the filters are not working.

To fix this, the Enatega team will likely need to:

  • Review the API calls: Ensure the app is sending the correct filter parameters to the backend.
  • Debug the filtering logic: Step through the code that handles filtering on the frontend to identify any errors.
  • Check data structures: Verify that the restaurant data is structured in a way that allows for efficient filtering.
  • Investigate caching mechanisms: Ensure that cached data is being updated when filters are applied.
  • Test UI elements: Confirm that the filter options are correctly linked to the filtering functions and that there are no visual glitches.

Conclusion

The filter bug in the Enatega Android app is a prime example of how seemingly small issues can significantly impact user experience. By providing a clear bug report with detailed steps to reproduce, the user has helped the development team immensely. Addressing this issue should be a high priority for Enatega, as functional filters are essential for a smooth and efficient restaurant ordering experience. Let's hope they squash this bug soon so users can get back to easily finding their favorite eats!