CityRyder

First login and partner onboarding

Opening CityRyder for the first time presents a login screen that asks for a username and a password. The registration process is not available directly within the app. New delivery partners must register through the CityRyder website. Once registered, the partner receives login credentials. The app then asks for permission to access the device's location. This is required for order tracking and navigation. The app does not explain why this permission is needed, which can be confusing. After logging in, the main dashboard loads. This dashboard shows a menu with options like "Orders," "Schedule," and "Settings." The interface is clean but minimal. There is no tutorial or walkthrough. New users must explore on their own. The "Orders" tab is the most prominent feature. It shows a list of available orders from darkstores, shops, and restaurants. Each order includes the pickup location, delivery address, and order details. Tapping on an order opens a detail view with the customer's location and a timer showing the remaining delivery time. The "Schedule" tab allows partners to view their shifts and availability. The "Settings" tab contains the presence/absence toggle, which activates or deactivates the partner's availability for accepting orders. The entire onboarding process takes about two minutes, assuming the user already has login credentials.

For partners who want to maximize their earnings, the app offers a "Presence" feature. This allows setting availability for accepting orders. When presence is activated, the app starts sending order notifications. When deactivated, the partner stops receiving orders. This is useful for managing work hours. However, the feature is not customizable. Partners cannot set specific hours or limit the number of orders. They have to manually toggle the presence setting on and off. This lack of automation is a common frustration among users.

When presence setting meets the delivery timer

The app's core value is enabling delivery partners to receive and fulfill orders efficiently. The presence/absence setting is the primary tool for this. A partner activates presence to start accepting orders. The app then shows available orders with pickup and delivery details. The partner selects an order, picks it up from the darkstore or restaurant, and delivers it to the customer. The app tracks each step with action confirmation buttons. This works well when the partner is actively working. However, the real test comes when the partner is managing multiple orders or when the delivery timer is running low. Suppose a partner accepts an order and the timer shows 30 minutes for delivery. The partner picks up the order but encounters traffic. The timer continues to count down. The partner must decide whether to rush or risk a late delivery. The app does not provide a way to extend the timer or to notify the customer of a delay. This puts pressure on the partner. Furthermore, if the partner has presence activated but is not actively checking the app, they might miss an order notification. The app does not send persistent notifications or reminders. This leads to missed opportunities. The clash between the presence setting and the timer creates a stressful experience. The app does not offer a way to pause the timer or to adjust the presence setting based on current workload. Partners are left to manage both manually.

Furthermore, the app's handling of order cancellations is also problematic. If a partner accepts an order but cannot fulfill it, they have to cancel it. The app does not provide a way to reassign the order to another partner. The order is simply removed from the system. This can lead to customer dissatisfaction. The original analysis here is that the app's architecture treats presence setting and timer as separate modules. They are integrated at the UI level, but the backend logic does not account for real-world scenarios like traffic or delays. This is a design flaw that is not apparent from reading the Play Store description.

Real-world performance during deliveries

User reports from various platforms paint a limited picture of the app's stability. Since the app is relatively new, there is limited feedback. Some partners praise the app for its ease of use and the ability to manage orders from a single interface. They appreciate the presence/absence toggle and the timer feature. However, others report issues with notification reliability. Several partners have complained that they do not receive notifications for new orders when the app is in the background. This is a significant problem because it reduces the app's utility for earning income. The app does not provide a way to test notification settings or to troubleshoot notification issues. Partners are left to guess whether notifications are working. Some partners have also reported that the app crashes occasionally, particularly when loading the order list or the timer. 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 details are accurate and easy to read. Partners can quickly see what items to pick up and where to deliver. The customer location is also displayed on a map, which is useful for navigation.

Another issue is the app's handling of offline access. Some partners have reported that the app does not cache order details for offline viewing. This is a problem in areas with poor internet connectivity. Partners have to rely on a stable connection to access any feature. The app does not provide a way to download order information for offline use. This is a significant limitation for users in areas with spotty coverage. The app also lacks a feedback or rating system. Partners cannot rate orders or provide feedback on the app itself directly within the app. They have to use external platforms. This limits the app's utility for the developer to gather real-time feedback.

Location permission and the changelog

The app requires location permission to show the customer's location 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: "Цього разу без суттєвих змін, проте додали дещо для вашої зручності та поліпшення досвіду взаємодії з застосунком." No specific bugs are named. No performance metrics are provided.