RideWest
Taking a Perth carpooling platform from idea to launch.
A WA-based carpooling experience for drivers and passengers: find or post a ride, choose a pickup point and stay connected with a travelling group.
Discuss your marketplace idea
- Sector
- Digital Products
- Story status
- Product showcase
- Focus
- Carpooling app design · Perth, WA
01 / The challenge
Start with the work,
not a feature list.
A carpooling marketplace needs two clear journeys: drivers offering seats and passengers finding a suitable trip. Search, pickup coordination and communication need to work together on a small screen.
RideWest is a WA-based carpooling product showcase. The supplied app and website presentations describe a marketplace with two sides: drivers offering a journey and passengers searching for a suitable seat. Designing that experience means making trip details, pickup choices and requests understandable across mobile and desktop. Perth provides the geographic context; the visuals do not establish user numbers, launch status or app-store availability.
02 / The approach
Carpooling app design · Perth, WA
- 01Find or post a ride
- 02Choose pickup
- 03Request a seat
- 04Driver review
- 05Trip coordination
- 06Travel together
Product journey illustrated by supplied screens; implementation scope is confirmed separately.
Give each visitor a clear starting point: find a ride, post a ride or join a group. The website presentations organise travel around daily commutes, long-distance journeys, group travel and special events.
Move from search into the details that make a ride suitable. The supplied screens show ride information, pickup-point selection and seat requests, with review and acceptance controls for the driver.
Support coordination beyond the first search. Groups, messaging, saved places and journey shortcuts are shown in the designs. Official store listings and precise delivery ownership remain unpublished until verified.
The product in practice
A closer look at the workflow.
Supplied product visuals show the capabilities discussed in this story. Screen counts are demonstration data, not measured business results.
03 / Product value
Turn a marketplace idea into a usable mobile experience for drivers and passengers.
Find a journey that fits
The supplied designs show origin, destination, date and seat search, alongside daily commute, long-distance, group and event journeys.
Coordinate pickup and requests
App screens show suggested pickup locations, ride details, pending seat requests and driver acceptance controls.
Stay connected
Groups, messaging, saved places and trip shortcuts support repeat journeys and communication.
Design through delivery
The showcase follows the product problem, driver and passenger journeys, interface design, mobile development and launch preparation. The exact delivery ownership and live store listings are not published until verified.
What to measure next.
These are review questions for evaluating the workflow, not achieved KPIs. Baselines and measured outcomes have not been supplied for publication.
- Journey clarity
- Can a driver and passenger each find their starting action?
- Pickup coordination
- Is the pickup location understandable before a seat request?
- Request progression
- Can both sides distinguish a pending request from driver acceptance?
04 / Evidence & status
What this story shows.
Supplied app and website visuals support the features described here. Exact delivery contribution, launch status and official app-store listings await verification; no store links, technology tags or customer metrics are invented.
Banner photography is AI-generated editorial illustration, not a photograph of the client, its staff or its premises. Product screens are the separately supplied visual evidence.
Explore a similar workflow
From this story to your next step.
A similar challenge?
Let’s talk about your workflow.
Work with our Adelaide-based team to identify the information, decisions and handovers your software needs to support.


