Ride Sharing App Design: Maps, Booking and Driver Screens
Ride sharing app design guide: rider booking flow, map and pickup UX, live trip states, safety features, payments and the driver app screens.

This guide is for founders, designers and developers working on a ride-sharing, taxi or delivery-style app. Ride sharing app design is mostly about one thing: making a real-time, map-heavy process feel calm and predictable, for two different users at once. You will get the rider flow screen by screen, the map and bottom sheet patterns that apps like Uber, Lyft, Bolt and Grab have converged on, the driver app essentials, safety features, and a checklist for edge cases.
TL;DR: Build the rider app around a map with a bottom sheet that changes as the trip progresses: where to → choose ride → confirm pickup → matching → driver arriving → on trip → rate and pay. Show price and arrival time before commitment, make the pickup point precise, and keep safety tools one tap away. The driver app is a separate product optimised for glanceability while driving.
Two apps, one system
A ride-sharing service usually ships at least two apps:
| Rider app | Driver app | |
|---|---|---|
| Main goal | Get from A to B with a known price and time | Accept good trips, navigate, earn |
| Context | Standing on a street, often in a hurry | In a moving car, hands mostly on the wheel |
| Session length | A few minutes of active use per trip | Hours online |
| Design priority | Clarity, trust, speed of booking | Glanceability, large targets, minimal reading |
The rider flow, screen by screen
1. Home: map plus "Where to?"
- •A full-screen map centred on the user's location, with a large "Where to?" search field.
- •Below it, shortcuts: saved places (Home, Work), recent destinations, and sometimes scheduled rides.
- •Nearby cars on the map give a live sense of availability.
- •Location permission is requested here, in context, with a clear reason ("To find drivers near you"). If denied, let users type a pickup address.
2. Destination search
- •Autocomplete results with place names first and addresses second.
- •Pickup and destination fields shown together, with pickup defaulting to "Current location" and editable.
- •Option to add a stop where the service supports it.
- •Choose on map as a fallback for places without good addresses.
3. Ride options
This is the comparison step. A bottom sheet lists ride types over a map with the route drawn.
| Element | Why it matters |
|---|---|
| Ride type name and vehicle icon | Recognition at a glance (standard, larger, premium, shared) |
| Price or price range | Upfront pricing is now expected; surprises erode trust |
| Arrival time or pickup ETA | Often the deciding factor |
| Capacity | Number of seats |
| A short qualifier | "Quiet ride", "Eco", "Pets allowed" |
| Selected payment method | Visible and changeable before confirming |
Default-select the option most people choose, keep the confirm button sticky at the bottom with the ride type in its label ("Confirm Standard"), and explain surge or high-demand pricing in plain language at this step, not after.
4. Confirm pickup
Pickup accuracy is the largest source of frustration in ride sharing. Dedicated pickup confirmation has become standard:
- •A draggable pin on the map with the address updating as the user moves it.
- •Suggested pickup spots (snapped to safe, legal points) for airports, stations and busy streets.
- •Clear text: "Meet at the north entrance, Gate 3".
- •For airports and large venues, step-by-step instructions or zones.
5. Matching
- •An animated state that shows the search is happening: "Finding your driver".
- •A cancel option without penalty during matching.
- •If matching takes longer than expected, say so and offer alternatives.
6. Driver on the way
The bottom sheet now becomes a driver card:
- •Vehicle first: licence plate in large type, car make, model and colour. Riders match plates, not faces.
- •Driver name, photo and rating.
- •ETA in minutes, and the car moving on the map along its route.
- •Actions: Call, Message (often masked numbers or in-app chat), Share trip, Cancel.
- •A PIN or code to verify the right car, where the service offers it.
Notify the rider when the driver is a minute away and when they arrive, and show a waiting-time indicator if fees apply after a grace period.
7. On trip
- •Route and current position, with an updated arrival time at the destination.
- •Safety toolkit button always visible.
- •Share trip status with contacts.
- •Option to change destination or add a stop.
8. Arrival, payment and rating
- •Automatic payment with a receipt summary: fare breakdown, tip option, payment method.
- •Rating with a 1–5 star scale and optional quick tags ("Great conversation", "Clean car"), with low ratings prompting a reason.
Map and bottom sheet patterns
The map plus bottom sheet layout is the backbone of ride-sharing UI. A few rules make it work:
- •Use a sheet with detents (collapsed, half, expanded). iOS sheets support custom detents natively; on Android, the Material bottom sheet behaves similarly.
- •Keep the critical action above the fold in every sheet state.
- •Fit the route to the visible map area, not the full screen — account for the sheet height when centring the route.
- •Simplify the map style: muted base colours, fewer points of interest, and high contrast for the route, pickup and car.
- •Respect safe areas: the "Where to?" field and floating buttons must clear the status bar and Dynamic Island, and the sheet's sticky button must clear the home indicator. The notch and safe area simulator helps check this on different devices.
- •Plan for dark mode: many trips happen at night, and a bright white map can be glaring. A dark map style with a lighter route line is common. See our dark mode app design guide for colour and contrast rules.
Safety features riders expect
- •Share trip with live location to chosen contacts.
- •An emergency button that connects to local emergency services and shows the trip details to read out.
- •Verify your ride: plate, car and optional PIN.
- •Driver and rider ratings, with the option to report issues after a trip.
- •Masked phone numbers for calls and messages.
- •Trusted contacts and safety check-ins if a trip stops unexpectedly or deviates from the route.
The driver app
The driver app is used while driving, so design for glances of a second or two.
Core driver screens
- •Go online: a large toggle or button, with earnings for the day and demand hints on the map.
- •Trip request: a full-width card with pickup distance and time, trip length or destination area (depending on the service's rules), estimated earnings, rider rating, and a countdown to accept. Huge Accept target; decline is a smaller secondary action.
- •Navigate to pickup: turn-by-turn navigation (in-app or handing off to a navigation app), rider name, pickup notes, Arrived button.
- •Pickup: confirm rider, PIN entry if used, Start trip slide control to avoid accidental taps.
- •On trip: navigation to destination, End trip slide control.
- •Trip complete: earnings for the trip, rating for the rider.
- •Earnings: daily and weekly totals, trip list, payouts, incentives progress.
- •Account and documents: licence, insurance, vehicle details, with expiry alerts.
Driver app design rules
- •Large tap targets, well above the 44pt and 48dp minimums — drivers tap at arm's length.
- •High contrast and large type for anything read while moving.
- •Audio and haptic cues for new requests.
- •Slide or long-press controls for irreversible actions like ending a trip.
- •Minimal text; numbers and icons carry most of the information.
Edge cases to design
| Situation | What to design |
|---|---|
| No drivers available | Clear message, ETA estimate, option to schedule or try another ride type |
| Driver cancels | Automatic rematching with an explanation, not a silent reset |
| Rider cancels after matching | Clear fee rules shown before confirming cancellation |
| Wrong pickup location | Easy pin edit, message driver, updated ETA |
| GPS drift | Smooth car movement on the map, no jumping icons |
| Payment fails | Retry with another method before the next trip, explained plainly |
| Lost connection | Last known status, automatic reconnection, trip continues |
| Long wait at pickup | Waiting timer and fee notice for the rider; wait timer for the driver |
| Airports and venues | Zone-based pickup instructions |
Ride-sharing app screen inventory
For a first version, design at minimum:
- •Rider: onboarding and sign-up, home map, destination search, ride options, confirm pickup, matching, driver arriving, on trip, receipt and rating, trip history, payments, safety centre, profile and settings.
- •Driver: sign-up and document upload, go online, trip request, navigate to pickup, pickup confirmation, on trip, trip complete, earnings, account and documents.
That is roughly 20 screens across both apps, plus states. You can generate a first draft of the rider screens in floow from a written brief, then focus your time on pickup confirmation, cancellations and safety flows. Before building, click through the full trip as a prototype with real riders — our guide on how to prototype an app explains how to run that test. For the full journey from design to launch, see how to build a mobile app.
Pre-launch checklist
- •Price and ETA are visible before the rider commits.
- •Pickup point is confirmed on a draggable pin with suggested spots.
- •Driver card leads with licence plate, car and colour.
- •Safety toolkit is one tap away during every trip state.
- •Each bottom sheet state keeps its main action visible.
- •Map is readable in daylight and at night.
- •Cancellation rules and fees are shown before confirming a cancellation.
- •Driver app uses large targets, high contrast and slide controls for irreversible actions.
- •Every edge case in the table above has a designed state.
FAQ
What screens does a ride-sharing app need?
A rider app needs home with map and search, destination search, ride options, pickup confirmation, matching, driver arriving, on trip, receipt and rating, history, payments, safety and settings. A driver app needs onboarding with documents, go online, trip requests, navigation, pickup, trip completion and earnings.
Why do ride-sharing apps use bottom sheets?
Bottom sheets keep the map visible while showing the information for each trip stage. They can expand for detail and collapse to show more map, and the main action stays within thumb reach at the bottom of the screen.
How do you design a good pickup experience?
Let riders confirm pickup on a draggable pin, suggest nearby safe and legal pickup spots, show clear text instructions for complex places like airports, and give both rider and driver a way to message each other. Leading the driver card with the licence plate helps riders find the right car quickly.
How is a driver app different from a rider app?
The driver app is used for hours, often while driving, so it prioritises glanceable information, large tap targets, audio and haptic cues, and controls that prevent accidental taps. The rider app focuses on fast, trustworthy booking and clear trip status.
Design it with floow
Draft the full rider trip, from search to rating, and refine each bottom sheet state in chat. Try this prompt in floow: "Design an iOS ride-sharing rider flow: home map with Where to search and saved places, ride options sheet with prices and ETAs, confirm pickup with draggable pin, driver arriving card with licence plate first, and trip receipt with tip and rating."
Design your mobile app with AI.
Generate pixel-perfect iOS and Android screens in seconds, then export to Figma or code.
You might also like…
Insights17 November 2026Recipe App Design: Search, Cook Mode and ListsRecipe app design guide: the core screens, ingredient scaling, hands-free cook mode, smart shopping lists and search filters, with specs and copyable prompts.By floow.design
Insights17 November 2026Mobile Checkout Design: 11 Patterns That ConvertMobile checkout design patterns that reduce abandonment: guest checkout, wallet pay, smart forms, clear totals and error handling, with specs and a checklist.By floow.design
Insights17 November 2026How to Make an iPhone App: Design, Build, ShipHow to make an iPhone app step by step: scope it, design iOS screens to Apple's rules, pick SwiftUI or cross-platform, test in TestFlight and pass App Review.By floow.design