Qooxy: Livraison à domicile

First order and account setup

Opening Qooxy for the first time presents a login screen that asks for a phone number and a password. The registration process is straightforward: enter a phone number, receive a verification code via SMS, and create a password. The app then asks for permission to access the device's location. This is required for showing nearby restaurants and for delivery. The app does not explain why this permission is needed, which can be confusing. After registration, the main dashboard loads. This dashboard shows a search bar at the top, a list of nearby restaurants, and a few categories like "Pizza," "Burgers," and "Sushi." The interface is clean but minimal. There is no tutorial or walkthrough. New users must explore on their own. The search bar allows searching by restaurant name, dish, or cuisine type. Tapping on a restaurant opens its menu with items, prices, and descriptions. Adding items to the cart is simple: tap the plus icon next to each item. The cart shows the total price, including taxes and delivery fees. The checkout process requires entering the delivery address and selecting a payment method. The app supports cash on delivery and card payments. The entire onboarding process takes about three minutes, assuming the phone number verification works without issues.

For users who want to track their order, the app offers a real-time tracking feature. After placing an order, the app shows the estimated delivery time and a map with the courier's location. The map updates as the courier moves. This is useful for knowing when to expect the delivery. However, the tracking feature is not always accurate. Some users have reported that the map shows the courier at a different location than where they actually are. This can be frustrating. The app also sends push notifications for order updates, such as when the restaurant confirms the order or when the courier is nearby. These notifications are helpful but not customizable. Users cannot choose which notifications to receive.

When order tracking meets estimated delivery time

The app's core value is enabling users to order food and track its delivery in real time. The order tracking feature is the primary tool for this. A user can see the courier's location on a map and the estimated delivery time. This works well when the courier's GPS signal is strong and the app's backend is responsive. However, the real test comes when the estimated delivery time changes. Suppose a user orders food and the app shows an estimated delivery time of 30 minutes. The user waits. After 20 minutes, the estimated delivery time updates to 45 minutes. The user is now confused and frustrated. The app does not provide a reason for the delay. The user has to guess whether the restaurant is busy or the courier is stuck in traffic. This clash between the tracking and estimated time features creates a stressful experience. The app does not offer a way to contact the courier or the restaurant directly. Users are left to wait without information. This is a significant limitation for a food delivery app.

Furthermore, the app's handling of order cancellations is also problematic. If a user wants to cancel an order, they have to contact customer support. The app does not provide a cancel button. This is inconvenient and time-consuming. The original analysis here is that the app's architecture treats order tracking and estimated delivery time as separate modules. They are integrated at the UI level, but the backend logic does not account for real-world scenarios like traffic or restaurant delays. This is a design flaw that is not apparent from reading the Play Store description.

Real-world performance and common issues

User reports from various platforms paint a mixed picture of the app's stability. Some users praise the app for its service and the ability to order from local restaurants. They appreciate the real-time tracking and the variety of restaurants available. However, others report issues with the user interface. Several users have complained that the app is confusing and difficult to navigate. This is a significant problem because it reduces the app's usability. The app does not provide a way to give feedback on the interface or to suggest improvements. Users are left to struggle with the design. Some users have also reported that the app crashes occasionally, particularly when loading the restaurant list or the map. The crashes are not frequent, but they are disruptive. The app does not display a crash report or offer to send logs to the developer. It simply disappears and returns to the home screen. Restarting the app usually resolves the issue temporarily. On the positive side, the app's order placement process is generally smooth. Users can quickly add items to the cart and checkout. The payment process is also straightforward.

Another issue is the app's handling of delivery addresses. Some users have reported that the app does not save their address correctly. They have to re-enter their address for every order. This is a minor but annoying issue. The app also lacks a favorites feature for restaurants. Users cannot save their favorite restaurants for quick ordering. This limits the app's convenience for repeat customers. The app's search function is also limited. It does not support filters for dietary restrictions or price ranges. This makes it difficult for users with specific preferences to find suitable restaurants. The app's notification system is also inconsistent. Some users have reported that they do not receive notifications for order updates. They have to open the app to check the status. This defeats the purpose of real-time tracking.

Location permission and the changelog

The app requires location permission to show nearby restaurants and to track deliveries. This is stated clearly during installation. However, the app does not explain why it needs this permission. Users are left to guess. The developer's changelog for the current version simply states: "Minor bug fixes and improvements." No specific bugs are named. No performance metrics are provided.