Comprehensive Shahem UI/UX Design

Shahm UI/UX Design Proposal Request

We are looking for a professional UI/UX designer or design agency to design the complete customer, service provider, and driver experience for Shahm across responsive web and mobile applications.

The entire project must be completed and delivered within a maximum of 10 days from the official start date.

About Shahm

Shahm is a digital platform that allows customers to request services and products through one simple interface.

The customer deals directly with Shahm, while Shahm manages service providers, suppliers, drivers, purchasing, pricing, fulfillment, payments, and operations in the background.

Shahm may include services such as water tankers, vehicle towing, sewage services, waste containers, transportation, equipment rental, building materials, suppliers, factories, contractors, and other operational services.

The customer should not need to search for suppliers, negotiate with multiple providers, or understand Shahm’s internal sourcing process.

The customer experience should be simple:

Select Service, Enter Details, Select Location, Review Price, Submit Order, Track Order, Receive Service.

In most services, the customer should only see simple statuses such as:

Order Received
Order Confirmed
In Progress
On the Way
Arrived
Completed

Internal supplier searching, provider rejection, dispatch rounds, and operational processes should generally remain hidden from the customer.

Project Scope

The design should cover three main experiences:

1. Shahm Customer
2. Shahm Service Provider and Supplier
3. Shahm Driver

Our immediate priority is a mobile-first Responsive Web App that works extremely well on smartphone browsers.

The same UX architecture and Design System should later be reusable for iOS and Android applications.

Customer Experience

The customer journey should include:

Mobile Login, OTP Verification, Home, Select Service, Order Form, Location, Attachments, Order Summary, Price, Payment, Submit Order, Track Order, Communicate with Shahm, Completion, and Rating.

Main customer screens should include:

- Login and OTP
- Home
- Services
- Service details
- Create order
- Location selection
- Map and location-link options
- Image, video, voice note, and PDF attachments
- Order summary
- Pricing
- Payment
- Order confirmation
- Active orders
- Order history
- Order details and timeline
- Notifications
- Chat with Shahm
- Profile
- Saved addresses
- Support

Communication is a major part of Shahm.

There should be strong communication between the customer and Shahm through in-app messages, notifications, and WhatsApp when required.

The objective is to maintain good follow-up, prevent missed deliveries, resolve delays, answer customer questions, and ensure successful order completion.

Service Provider Experience

A Shahm provider may be a driver, vehicle owner, fleet owner, supplier, store, factory, contractor, company, or service team.

The design therefore must be flexible and should not be built around only one provider type.

Provider onboarding should include:

Mobile Number, OTP, Name Confirmation, Provider Type, Activity, Business Details, Assets, Documents, Bank Account, Coverage Area, Services, Approval, and Start Receiving Orders.

Provider screens should include:

- Registration
- Provider type and activity
- Business information
- Documents
- Asset registration
- Asset photos
- Driver assignment
- Coverage area
- Bank account
- Account review
- Home dashboard
- Receiving Orders On or Off
- Operating capacity
- New orders
- Order details
- Accept or Reject
- Submit quotation
- Active orders
- Completed orders
- Assets
- Drivers
- Messages
- Notifications
- Wallet
- Earnings
- Transactions
- Withdrawals
- Support

Order cards should clearly display the service type, approximate location or distance, provider earnings, response countdown, and required action.

Some orders will use Accept or Reject, while quotation-based services will use View Details and Submit Quotation.

Operating Capacity

The provider interface should clearly show operational capacity.

For example:

Operating Capacity: 0 / 1

or

Operating Capacity: 3 / 5

When capacity is full, the provider should stop receiving new eligible orders until capacity becomes available again.

Driver Experience

The driver experience should be simpler and focused on execution.

Main screens should include:

- Availability
- Current task
- Task details
- Pickup location
- Delivery location
- Open navigation
- Start task
- Arrived at pickup
- Loading completed
- Heading to customer
- Arrived at customer
- Start delivery
- Delivery completed
- Proof of completion
- Unable to complete task
- Contact Shahm
- Notifications
- Task history

Provider Wallet and Payments

Initially, new providers may receive fast payments after completing orders.

A clear banner should communicate this, for example:

Fast Payment Active

Your earnings will be processed quickly after each completed order during your first 10 days.

Later, providers should transition to the Shahm Wallet.

The wallet should display:

Current Balance
Available Balance
Pending Balance
Total Earnings
Transaction History

Providers should be able to request withdrawal to an approved bank account.

Withdrawal statuses should include:

Under Review
Approved
Transfer in Progress
Transferred
Rejected or Needs Modification

Communication

Communication must also exist between Shahm and the service provider, and between Shahm and the driver.

The platform should support:

- In-app messaging
- Notifications
- Text messages
- Voice messages
- Images
- Files
- WhatsApp communication when required

This communication is essential for order execution, delivery coordination, issue resolution, customer follow-up, provider follow-up, and successful order completion.

Design Requirements

The design should be modern, professional, simple, mobile-first, suitable for the Saudi market, excellent in Arabic RTL, adaptable to English LTR, easy for non-technical users, and scalable for future services.

A complete Design System is required, including:

- Typography
- Colors
- Buttons
- Cards
- Inputs
- Navigation
- Status components
- Dialogs
- Alerts
- Upload components
- Order cards
- Empty states
- Error states
- Loading states

Deliverables

The final delivery must include:

- UX Architecture
- User Flows
- Sitemap
- Screen Map
- Wireframes
- High-Fidelity UI
- Responsive Web Designs
- Required Mobile App Screens
- Design System
- Component Library
- Interactive Figma Prototype
- Error and edge cases
- Developer Handoff
- Organized Figma files
- Arabic-first design with an English-ready structure

10-Day Delivery Requirement

The project must be fully completed within 10 days.

We expect continuous progress sharing throughout the project rather than receiving everything on the final day.

The proposal should include the total cost, estimated screen count, number of revision rounds, team size, relevant previous work, delivery approach, and confirmation of the 10-day delivery commitment.

The final objective is to create a product where customers can request services as easily as ordering a ride, while providers and drivers receive a clear operational system for receiving, executing, tracking, and getting paid for orders.

The result must be a complete, scalable, developer-ready UI/UX experience, not simply a collection of attractive screens.