(Ride-Hailing Ecosystem: Mobile + Web ERP)

Senior UI/UX Designer (Ride-Hailing Ecosystem: Mobile + Web ERP) -

A detailed technical specification is already available, with a complete description of all logic and each screen.
Dear colleagues, please: if you are not a Senior UI/UX designer — do not write. We do not need help - we need a specialist who understands 120% what a ride-hailing platform is.
Please send real work from mobile applications where you personally created the design. We do not consider mythical renders.
Thank you for your understanding.

About the project: this is a large international ecosystem for ordering rides. We are creating not just a design, but an engineering system where 70% of components are unified across applications, and the interface directly affects the speed of decision-making in real time.

We need a systematic designer who can work with Design Tokens, understands the specifics of Map-First interfaces, and is ready to design 148+ screens for iOS, Android, and Web.

🛠 Scope of Work: 148 screens + Marketing

1. Rider App (iOS & Android) - ~27 screens

The entire user journey: from login (OTP) to trip rating.

Map-First UI: Main screen without Top Bar, management through floating widgets.

Rider Boost: Interface for real-time price bidding system (“Flash” effects when the price changes).

Live Activity: Tracking car arrival and route.

2. Driver App (iOS & Android) - ~26 screens

Onboarding & KYC: Complex flow for uploading 6+ photos of the car and documents.

Incoming Order: Order acceptance screen (Full Screen Intent) over phone lock.

Shift & Earnings: Earnings statistics, G-Wallet balance.

3. Admin Panel (Web ERP) - ~44 pages

Framework-ready Design: Designing the interface with strict consideration for using ready-made React libraries (shadcn/ui or MUI) to speed up layout.

Evidence Console: Complex dispute arbitration widget (map “Plan vs Fact” + telemetry).

Dispatch & Surge: Managing geofences (Polygon Tool) and heat maps.

4. Web Tracking Client (Mobile Web)

Adaptive page for public ride sharing (viewing the route in a browser without the app).

5. Marketing Assets (App Store & Google Play)

Screenshots: Preparation of 6–8 promotional screenshots for each app (Rider/Driver) with device mockups and marketing texts.

Icons: Development of a set of app icons for all extensions (iOS/Android).

⚙️ Technical Standards and Requirements

1. Foundation & Branding

Work strictly according to the provided Brand Book.

Typography: Poppins (Bold/Medium for headings, Regular for text).

Grid: Strict 8dp/8px grid.

2. Technological Dark Theme (Adaptive UI)

⛔ PROHIBITED: Manually repainting each layout in dark color.

✅ REQUIREMENT: Implementation of dark theme through Design Tokens (Variables) system in Figma. All colors (Background, Surface, Text-Primary) must be tied to variables so that developers can change the theme at the code level with one line.

3. UI Kit for developers

States: Detailing all states of elements: Normal, Pressed, Disabled, Loading.

Anti-Flicker: Mandatory design of Skeleton Loaders (flickering placeholders) for all lists and cards to avoid “jumps” in the interface during loading.

4. Splash Screen

Designing the startup screen considering native animation: smooth Fade-in of the logo in exactly 800 ms (without complex 3D effects).

5. Map-First Design

Deep styling of maps (Custom Google Maps JSON Style) for light and dark themes.

Designing layers of Heatmap (hexagonal grid) and logic for car marker movement (smoothness, turns).

✅ Handoff Readiness Checklist

You are considered ready to hand over layouts to developers (Developer Handoff Meeting) when the following is completed:

[ ] All screens are completed and checked in light/dark modes.

[ ] Design System is documented (colors, tokens, fonts, spacing, shadows).

[ ] Components Library is ready (all master components are assembled and structured).

[ ] Assets are exported (icons in SVG, illustrations, Lottie animations).

[ ] Interaction Flows are described (prototypes of transitions and logical connections are created).

[ ] Responsive Specs are ready (adaptability for different screen sizes of iPhone/Android).

[ ] Accessibility is considered (contrast WCAG AA, touch areas ≥ 44pt).