A delivery rider’s mobile app needs to make the next task obvious. When users are moving between pickups, deliveries, and customer locations, unclear language, dense screens, or unnecessary steps can make even simple actions harder to complete.
Desisle designed a bike delivery service mobile application for the UAE from the ground up. The work focused on creating a straightforward, user-centred experience for delivery personnel, with clear navigation, minimal technical jargon, and task flows designed to be easy to understand.
Project Overview
- Industry: Delivery services
- Product: Bike delivery service mobile application
- Market: United Arab Emirates
- Primary users: Delivery personnel
- Services: UI/UX design
- Role: UI/UX Designer
- Team: One UI/UX Designer and two stakeholders
- Project period: 2023-2024
What Did Desisle Do?
Desisle led the UI/UX design of a rider-facing mobile application for a bike delivery service in the UAE. The engagement included competitor research, delivery-app research, feature ideation, initial screen designs, development-ready assets, and design guidance intended to help the development implementation follow the approved concepts.
The Product Challenge
The product began as a new service concept, without an existing app interface to refine. This made early product-design decisions especially important: the team needed to understand common delivery-app patterns, define useful features, and establish an interface that could serve delivery personnel with varied levels of technical familiarity.
The objective was clear: create an end-to-end mobile-app design that reduced complexity rather than adding it. The product needed to help users move through delivery tasks without relying on technical language or lengthy instructions.
Designing for Delivery Personnel
Delivery personnel typically need to interact with an app while managing practical, time-sensitive work. That means the most useful interface is not necessarily the one with the most features visible at once. It is the one that clearly communicates what matters now and what action should follow.
The design therefore focused on the following principles:
- Clear navigation paths: Help riders understand where to go next within the application.
- Concise task instructions: Communicate essential information without unnecessary wording.
- Recognisable visual cues: Make important actions and statuses easier to identify.
- Minimal steps for common actions: Keep frequent interactions straightforward.
- A consistent interface language: Maintain familiar patterns throughout the experience.
This approach aimed to make the application approachable for both experienced app users and people who may be less confident with technology.
Recommended visual: A rider journey diagram from accepting a task through completing a delivery.
Why it matters: It explains the operational context behind the UI decisions.
Researching the Delivery-App Landscape
The design process included competitor research, delivery-app research, and consideration of delivery-service workflows. This work helped establish a foundation for feature ideation and interface direction before high-fidelity screens were created.
The purpose was not to duplicate existing delivery applications. It was to understand familiar user patterns, identify the type of information delivery personnel may need during tasks, and create an experience appropriate for a new service entering the UAE market.
Key UX Decisions
1. Reduce Technical Language
Problem: Delivery personnel may have different levels of technical proficiency, and complex system terminology can make tasks harder to understand.
Decision: Use simple, concise instructions and visual cues throughout the interface.
Why: Clear language helps users understand actions without requiring familiarity with technical product terms.
Trade-off: Shorter labels and instructions need careful prioritisation so important information is not removed in the name of simplicity.
2. Keep Task Flows Focused
Problem: Delivery work involves repeated task completion, so additional steps can create unnecessary friction.
Decision: Structure common interactions around minimal steps and straightforward navigation.
Why: The user experience needed to support quick comprehension and task completion.
Trade-off: Streamlined flows require clear sequencing so users always understand their status and next action.
3. Use a Modern, Minimal Visual System
Problem: Dense interfaces can overwhelm users, especially when the product is new.
Decision: Apply a clean, modern UI with minimalist design elements.
Why: A consistent and restrained visual language can improve clarity and make navigation feel more predictable.
Trade-off: Minimalism must still provide sufficient visual hierarchy to distinguish actions, statuses, and instructions.
The Designed Experience
The completed design established a rider-focused mobile interface for a UAE bike delivery service. It brought together task-oriented navigation, concise instructions, visual cues, and a consistent design language intended to support delivery personnel throughout their journey.
The designed experience focused on the following elements:
- Task-oriented navigation for delivery personnel.
- Clear instructions and easily recognisable visual cues.
- A consistent visual language across the application.
- Simplified interaction flows for common delivery tasks.
- A modern, minimal interface designed around usability.
Desisle also provided design assets for development and guided the execution process so the built experience could reflect the approved screen designs and interface concepts.
Recommended visuals:
- Main rider dashboard or task overview.
- Delivery-task detail screen showing key instructions and actions.
- Navigation, task-status, or delivery-completion state.
- UI component sheet showing buttons, status indicators, cards, and visual patterns.
Outcome
The project delivered a clean, modern, rider-facing application design focused on navigation clarity and ease of use. The supplied project information identifies a consistent interface language, user-friendly task flows, concise instructions, and visual cues as key outcomes of the design work.
Initial stakeholder feedback was described as positive, particularly regarding usability and design quality. No approved direct quote was supplied, so that feedback should not be formatted as a public client testimonial.
No post-launch product data was provided for this case study. Desisle does not attribute delivery-time improvements, rider productivity gains, retention, adoption, revenue, or operational results to this design work.
What We Learned
For delivery applications, user-centred design starts with respecting the conditions in which people use the product. A rider-facing interface must communicate essential information quickly, without assuming that every user has the same familiarity with mobile software.
The project reinforced the importance of research when designing for a new market. Competitor and workflow research can provide useful context, but the final interface must remain grounded in the product’s own users, service model, and operational needs.
Building a Similar Delivery Product?
Delivery and logistics products often need to support task-focused work without overwhelming users with system complexity. A useful starting point is mapping the user’s most frequent actions, identifying the information needed at each moment, and designing the shortest understandable path through those tasks.
Desisle can support founders and product teams designing mobile, web, and SaaS products that need a clear interface, structured user flows, and development-ready UI assets.
FAQ
What Type of Product Was Designed?
The project was a mobile application for a bike delivery service operating in the UAE.
Who Was the App Designed For?
The primary audience was delivery personnel, including users with different levels of technical confidence.
What Was Desisle’s Role in the Project?
The verified role included UI/UX design, competitor and delivery-app research, feature ideation, initial screen designs, development assets, and design-execution guidance.
Was the Application Designed From an Existing Product?
No. The supplied project context states that the experience was created from scratch.
Are Performance Results Available?
No verified post-launch metrics were supplied. The case study should not claim changes in delivery speed, productivity, retention, user growth, ratings, or revenue.