Mobility as a Service (MaaS) UX design implies designing seamless experiences that help users discover, plan, book, pay for, and complete their journey across numerous forms of transport through a single platform. It’s about removing friction throughout the whole mobility process, from route planning and ticketing to real-time navigation and post-trip engagement.
Earlier, mobility was synonymous with ownership. If you wanted freedom to move around, you simply bought a car. But that assumption is changing now. Across cities worldwide, people are choosing access over ownership. That means hopping between ride-hailing services, public transit, bike-sharing networks, and micromobility options within the same journey.
This shift is fueling the rise of Mobility as a Service (MaaS), a market projected to grow from USD 5.7 billion in 2023 to USD 40.1 billion by 2030. MaaS is a transportation innovation, of course. But it comes with real UX challenges.
In this guide, we’ll lay bare what defines great MaaS UX, the challenges mobility teams face, and the design principles and real-world examples driving the future of urban transportation.
What is Mobility as a Service (MaaS)?
Mobility as a Service (MaaS) is an innovative transport paradigm that enables consumers to plan, book, and pay for a journey through a single digital interface. Here, consumers can access several means of travel and can book the one that fits their requirements. Rather than purchasing a car, customers tap into a network of mobility options, including public transit, ride-hailing, bike-sharing, car-sharing and micromobility through one integrated experience.
Also Read: What is Automotive UX? Core Principles Explained
Why Mobility is Shifting From Ownership to Access
Mobility is shifting from ownership to access because people increasingly value convenience, flexibility, and affordability over owning a private vehicle. Rising urbanization, traffic congestion, environmental concerns, and the growth of digital platforms have accelerated the need for on-demand, shared, and multimodal transportation services. In fact, studies reveal that 65% of consumers are inclined to opt for end-to-end mobility services over vehicle ownership.
A closer look makes it easy to see that the winds of change in mobility are no different. Indeed, it is following the same direction as other businesses such as entertainment, software, and media, where access is sometimes more important than ownership.
For example, customers no longer buy CDs to listen to music but stream it. They don’t buy boxed software anymore. They subscribe to it. There’s also a growing acceptance of transport as a service that people may call upon when they need it, rather than an asset to own.
Capgemini's research found that convenience remains the biggest driver of mobility subscriptions, with nearly three-quarters of consumers citing it as their primary reason for choosing subscription-based services. Cost savings, flexibility, and freedom from maintenance responsibilities follow closely behind. These trends point to the fact that people are increasingly valuing effortless access to mobility over the commitment and complexity of ownership.
Whim (Helsinki): The MaaS Pioneer That Reimagined Urban Mobility
When discussions about Mobility as a Service begin, Whim is often the first platform mentioned. Launched in Helsinki by MaaS Global, Whim is widely regarded as one of the world’s earliest and most influential MaaS implementations. The app doesn’t work anymore, yet it is the ultimate pioneer of integrated urban transit.
Whim provided users with a single interface to plan, book, and pay for multiple types of transport. It incorporated public transit, taxis, bike sharing, and vehicle rentals into one trip. The platform also developed new pay-as-you-go and subscription-based mobility options that were greatly inspired by the way streaming services revolutionized media consumption.
Image Source: IF DesignEven though it faced long-term commercial scaling challenges, Whim completely shifted industry thinking from transportation-centric to user-centric. And for UX designers, it remains a gold standard benchmark for how integrated ticketing, planning, and payments can eliminate friction in public infrastructure.
MaaS vs Traditional Transportation: What’s the Difference?
| Traditional Transportation |
Mobility as a Service (MaaS) |
| Vehicle ownership is central |
Access to mobility is central |
| Different providers operate independently |
Services are integrated into one platform |
| Users plan journeys manually |
Platforms recommend optimized journeys |
| Multiple apps and payment systems |
Unified booking and payment experience |
| Limited personalization |
Context-aware recommendations and routing |
| Focus on vehicles |
Focus on user outcomes |
The distinction may appear subtle, but it fundamentally changes the design challenge.
That’s because traditional transportation products optimize individual services, but MaaS platforms optimize entire journeys.
The Four Levels of MaaS Maturity
Mobility as a Service apps exist on a spectrum. Some platforms simply help users discover transportation options, while others orchestrate entire journeys across multiple providers with minimal user effort. The difference lies in the level of integration.
Understanding these maturity levels helps explain why some mobility experiences feel fragmented while others feel seamless.
Level 0: No Integration
At this stage, transportation services operate in silos.
Users must manage every aspect of their journey themselves, right from comparing routes and checking schedules to booking tickets and making payments across different platforms.
Say, you are planning a trip that requires a metro ride, a bike-sharing service, and a taxi. You might need three separate apps, three separate accounts, and multiple payment transactions just to complete a single journey.
The burden of coordination falls entirely on the user.
Level 1: Information Integration
The first step toward MaaS is bringing information together.
At this level, users can view transportation options, schedules, routes, and estimated travel times through a single interface. However, when it’s time to book or pay, they are redirected to individual service providers.
Think of it as a mobility dashboard rather than a true MaaS platform. The user gains visibility, of course. But convenience? Not much.
Level 2: Booking and Payment Integration
Users must be able to find transportation options and book and pay for multiple services on the same site. They can process transactions from one interface, rather than juggling different apps and payment systems.
For users, the experience goes from merely examining alternatives to acting on those decisions.
Level 3: Service Integration
At this stage, MaaS begins delivering on its core promise.
Transportation providers work together as part of a connected mobility ecosystem. Users can plan, book, pay for, and navigate multimodal journeys without constantly thinking about individual operators or service boundaries.
A journey involving a metro ride, shared bike, and ride-hailing service feels like one continuous experience rather than three separate ones.
Level 4: Mobility Ecosystem Integration
The platform becomes an intelligent mobility orchestrator, dynamically recommending transportation options based on factors such as:
- User preferences
- Real-time traffic conditions
- Service availability
- Cost considerations
- Sustainability goals
- Historical travel behavior
Rather than asking users to choose among multiple options, the system proactively recommends the most relevant journey for the given context. In many ways, the platform evolves from a transportation tool into a mobility assistant.
Imagine opening an app and seeing:
"Heavy traffic on your usual route today. Taking the metro and completing the last mile via bike-sharing will get you to work 12 minutes faster."
That’s the promise of Level 4 MaaS.
What Technologies Power MaaS?
From the user's perspective, a MaaS experience should feel effortless. Behind the scenes, however, it relies on a sophisticated technology ecosystem. Several technologies make MaaS possible:
Real-Time Data Systems: Live information about schedules, delays, traffic conditions, and service availability.
GPS and Location Intelligence: Accurate positioning enables route planning, tracking, and multimodal navigation.
Open APIs: Allow multiple transportation providers to exchange information and connect services.
Artificial Intelligence: Supports route optimization, demand prediction, dynamic pricing, and personalized recommendations.
IoT Infrastructure: Connected vehicles, charging stations, scooters, bikes, and transportation networks provide continuous operational data.
Digital Payments: Unified payment experiences enable users to move between transportation modes without repeated transactions.
Defining MaaS UX: What Does User Experience Mean in Mobility?
MaaS UX (Mobility as a Service User Experience) is the complete experience of searching, planning, booking, paying, navigating, and completing journeys across various forms of transport via a single platform. In addition to displays and interactions, MaaS UX includes physical mobility touchpoints, real-time transportation systems, and service ecosystems, which makes it different from typical app UX.
The Five Layers of MaaS UX
At Onething Design, we believe successful MaaS experiences can be understood through five interconnected layers.
1. Discovery: Assisting Users in Understanding What is Possible
All journeys start with a question: “What’s the best way for me to get there?”
In order to make a decision, people need to know what options are accessible to them. That’s what the Discovery layer is for.
At this point, users are looking at routes, checking availability, comparing travel times, and thinking about costs. They’re trying to navigate an increasingly complex transportation scene that may include public transit, ride-hailing services, bike-sharing networks and micromobility possibilities.
The problem is that more information does not necessarily mean better clarity. An excellent discovery experience silently whittles down the options, presenting only the most relevant alternatives for the context, preferences, and goals of the user.
The aim of discovery in MaaS is to help the user identify the correct route, not to list all alternative routes.
2. Decision: Turning Information into Confidence
Once users understand their options, they face a different challenge, that is, choosing among them. This is where many mobility experiences unintentionally create friction.
A platform may present six different routes, each with varying travel times, costs, transfer requirements, and sustainability impacts. While this appears helpful, it often leads to something designers rarely account for. And yes, that is decision fatigue.
Naturally, people won’t want to spend their morning comparing transportation scenarios. They want confidence that they’re making the right choice.
The Decision layer focuses on reducing uncertainty through:
- Contextual recommendations
- Intelligent defaults
- Clear trade-offs
- Personalized suggestions
Instead of asking users to evaluate every possibility, the platform acts as a guide, helping them make informed decisions with minimal cognitive effort.
3. Booking: Converting Intent into Action
A user who has chosen a route has already done the hard work. Now comes the moment of commitment.
The Booking layer is where intent becomes action through ticket purchases, ride confirmations, reservations, subscriptions, and payments. This is also where many journeys are lost.
Every additional screen, form field, login prompt, or payment step creates friction. And in mobility, friction is costly because users are often operating under time pressure. They may be rushing to work. Or they can be on their way to catch a train or navigating an unfamiliar city. Or simply looking for the fastest way home.
The most effective MaaS experiences recognize this reality. They streamline transactions, unify payment flows, and remove unnecessary barriers between decision and action. Because when users are ready to move, the platform shouldn't slow them down.
4. Transit: Supporting Users When It Matters The Most
Most digital products consider the transaction the finish line.
MaaS UX doesn’t have that luxury. A mobility journey truly begins once the booking is complete. This is the stage where users navigate stations, wait for vehicles, manage transfers, adapt to delays, and respond to changing conditions in real time.
When everything goes according to plan, users barely notice the platform. But when plans change, they expect guidance.
The Transit layer focuses on helping users stay informed and in control through:
- Real-time updates
- Navigation assistance
- Delay notifications
- Transfer guidance
- Alternative route recommendations
The best MaaS experiences behave less like transportation apps and more like invisible travel companions, providing support whenever it's needed.
5. Trust: The Layer That Holds Everything Together
Trust is not limited to one stage of the journey, unlike the other layers. It’s there in all of them.
MaaS platforms are highly trusted by users. They disclose their location, their payment details, their travel habits, and their preferences, all with the expectation of a dependable, transparent, and secure experience. And they evaluate trust continuously.
Every clear explanation during a disruption strengthens the relationship. Users may tolerate occasional inconvenience but not broken trust.
After all, good mobility UX is about feeling confident that the platform guiding you there has your best interests in mind.
UX vs UI in MaaS: Why the Difference Matters
One of the most common misconceptions in mobility design is treating UX and UI as interchangeable concepts. Obviously, they are not.
UI (User Interface)
UI focuses on:
- Layouts
- Visual design
- Components
- Buttons
- Navigation structures
It determines how the interface looks and behaves.
UX (User Experience)
UX encompasses the entire journey.
In a MaaS context, that includes:
- Route planning
- Booking flows
- Payment experiences
- Physical wayfinding
- Transit interactions
- Customer support
- Trust and reliability
A user can love the interface and still hate the experience.
Consider a scenario where an app looks beautiful but fails to notify users about a missed transfer. The UI succeeded, of course, but the UX clearly failed.
This distinction is especially important in MaaS because the experience continues long after users leave the screen.
The User Journey in MaaS: Mapping Every Touchpoint
A MaaS user journey encompasses every interaction a person has while planning, booking, paying for, navigating, and completing a trip across multiple transportation modes. Mapping this journey helps designers identify friction points, reduce cognitive load, and create seamless mobility experiences that feel like a single connected service rather than a collection of disconnected providers.
The 6-Stage MaaS User Journey
We view MaaS experiences through six interconnected stages at Onething Design. Cumulatively, they represent the complete lifecycle of a mobility experience.
| Stage |
User Goal |
Primary UX Challenge |
Design Opportunity |
| Awareness |
Understand available options |
Information overload |
Simplify discovery |
| Onboarding |
Get started quickly |
Registration friction |
Reduce setup effort |
| Trip Planning |
Choose the best route |
Decision fatigue |
Intelligent recommendations |
| Booking & Payment |
Confirm transportation |
Transaction complexity |
Unified booking flows |
| In-Transit |
Reach the destination smoothly |
Uncertainty and disruptions |
Real-time guidance |
| Post-Trip |
Reflect and return |
Weak retention loops |
Build trust and loyalty |
Stage 1: Awareness
Before users can choose a route, they must understand what choices exist. This sounds obvious.
Yet many mobility products overwhelm users with transportation data before helping them make sense of it.
Users are often confronted with:
- Multiple transport modes
- Numerous route combinations
- Dynamic pricing
- Varying travel times
- Environmental considerations
The challenge here is excessive information. Great MaaS experiences act as interpreters. They transform transportation complexity into understandable choices.
Instead of displaying every possible route, they prioritize relevance. So, users need to be provided with meaningful recommendations so that they can make confident decisions.
Stage 2: Onboarding
Most mobility products lose users before they ever complete a trip because onboarding often feels like gargantuan work. Before a user can experience value, they’re frequently asked to:
- Create an account
- Verify identities
- Add payment methods
- Enable permissions
- Configure preferences
Certain fields are undoubtedly vital. However, requesting information in certain fields that could have been deferred to a later stage in the process may have contributed to lower app abandonment rates.
The best mobility experiences embrace principles such as:
- Progressive Disclosure: Ask only for the information needed at the current moment. Additional details can be collected later.
- Permission Timing: Request permissions when their value is obvious. Users are more likely to share location access when they understand how it improves route recommendations.
- Fast Time-to-Value: The quicker users see useful transportation options, the more likely they are to continue. A good onboarding flow doesn't feel like registration. It feels like the beginning of a journey.
Stage 3: Trip Planning
If there is one screen that determines the success of a MaaS platform, it is the trip planning experience. After all, this is where users make decisions.
Imagine being presented with:
- Metro option
- Bus option
- Ride-hailing option
- Bike-sharing option
- Multimodal option
Now add:
- Cost comparisons
- Travel times
- Transfer complexity
- Carbon emissions
- Real-time disruptions
What appears comprehensive can quickly become overwhelming. This phenomenon is known as the paradox of choice.
More options don't necessarily improve experiences. Sometimes they make decisions harder. Therefore, instead of displaying transportation modes equally, good mobility products prioritize recommendations based on user intent.
Designing Better Multimodal Experiences
Multimodal mobility is all about combining different transportation modes into a single journey. And honestly, that’s what makes MaaS equally powerful and challenging to design.
Let’s take the example of a typical commute.
You walk a few minutes to the nearest metro station, take a train across the city, pick up a shared bike outside the station, and cycle the final stretch to your destination. On paper, it’s an efficient journey.
In reality, it can quickly become overwhelming if users are left to figure out the details themselves.
Questions start piling up:
- Which exit should I take after leaving the station?
- How much time do I have to make the transfer?
- Will a bike actually be available when I get there?
- What happens if my train is delayed?
- Is there a backup option if part of the journey falls through?
These moments of uncertainty are where multimodal experiences are tested.
To the user, the journey should not seem like a collection of unrelated transit providers sewn together. They shouldn’t have to flip their minds back and forth between transit operators, maps, payment systems, or mobility apps every few minutes. Instead, each mode should flow into each other smoothly. This is why information architecture is so important in MaaS UX. Every screen, notification, and recommendation should reduce uncertainty and help users maintain momentum.
Stage 4: Booking and Payment
A user can spend several minutes comparing routes, weighing costs, and evaluating travel times. But none of that matters unless they’re willing to take the final step and commit to the journey.
Historically, one of the biggest barriers to MaaS adoption has been fragmentation. A user might discover the ideal route in one app, only to be redirected elsewhere to complete a booking or make a payment. What should feel like a seamless experience suddenly becomes a series of disconnected interactions.
From a user’s perspective, a redirect, additional login, or separate payment flow may seem like small inconveniences. But collectively, they break momentum and weaken confidence in the experience. This is precisely why integrated booking and payment experiences have become a hallmark of mature MaaS platforms.
Whether a user is purchasing a metro ticket, reserving a shared bike, or booking a ride-hailing service, the experience should feel unified. They shouldn’t have to think about which provider is handling the transaction or how many systems are involved behind the scenes.
The best mobility experiences make payment almost invisible. While pay-as-you-go models currently account for the majority of MaaS usage, subscription-based mobility plans are gaining traction as users increasingly value convenience and simplified access to transportation services.
Speaking from a UX perspective, both models are trying to solve the same problem, you see. That is, reduce transaction effort.
The less attention users have to devote to booking tickets, managing providers, or completing transactions, the more seamless the journey feels. And in MaaS, that feeling of effortlessness is often what separates a one-time user from a loyal one.
Stage 5: In-Transit
Many mobility products treat booking as the finish line. However, in reality, it is the halfway point.
Once a journey begins, users face a new set of challenges:
- Is my vehicle arriving?
- Am I heading in the right direction?
- What happens if something changes?
This stage is where trust is truly earned. Real-time information, therefore, becomes essential:
- Live Tracking: Visibility into vehicle locations and arrival estimates
- Disruption Management: Clear communication when delays occur
- Transfer Guidance: Support during transitions between transportation modes
- Alternative Recommendations: Fallback options when plans break down
The best MaaS experiences are those that behave like proactive travel companions. They anticipate problems before users encounter them.
Stage 6: Post-Trip
Do you know that some of the most important UX opportunities emerge after the trip is over?
Many mobility products treat arrival as the finish line. Once the transaction is complete, the experience simply ends. But the most successful MaaS platforms understand that the post-trip stage is where long-term relationships are built. It’s where users pause and decide whether the experience was worth repeating. This is also the moment when a platform can reinforce the value it delivered. This is also the moment when a platform can reinforce the value it delivered.
A well-designed post-trip experience might include:
- Trip summary for a quick recap of the trip
- Digital receipts for easy tracking of expenses
- Sustainability insights, such as carbon emissions avoided
- Loyalty credits accrued
- Opportunities to give feedback
Collectively, they help transform a completed trip into a memorable experience. More importantly, they remind users why they chose the platform in the first place.
One particularly effective approach emerging across MaaS platforms is behavioral reinforcement. Rather than simply telling users that a journey is complete, the platform highlights the impact of their choices.
For example:
- This month you’ve cut CO₂ emissions by 12 kg.
- This is your 5th public transport ride this week.
- You saved ₹1,100 on your mobility subscription this month.
These feedback loops help users see tangible outcomes from their decisions and reinforce behaviors the platform wants to encourage. People are more likely to repeat actions when they can clearly see the value those actions create. The same principle applies to mobility.
A commuter may not remember every route they took this month. But they may remember that they saved money, reduced their environmental impact, or avoided the stress of driving in traffic.
So yes, to sum up, the best post-trip experiences leave users with a feeling that extends beyond reaching a destination. They create a sense of progress, accomplishment, or confidence that makes returning feel like the obvious choice.
5 MaaS UX Design Patterns Shaping the Future of Mobility
While discussing MaaS UX, it is vital to take a look at certain UX patterns that are emerging repeatedly across successful mobility ecosystems. Irrespective of someone trying to choose the fastest route, managing multiple payments or navigating a disruption, these patterns help reduce friction at critical moments in the journey.
1. Smart Journey Suggestions
Most mobility apps begin with a blank search bar and a simple question: Where would you like to go? But for many users, the answer is surprisingly predictable.
Daily commuters often travel between the same locations – home, work, school, transit hubs, or favorite destinations. Asking them to manually search for the same journey every day creates unnecessary effort.
Smart Journey Suggesters solve this by using contextual signals such as time of day, location, travel history, and traffic conditions to proactively recommend routes before users begin searching.
Instead of starting with a blank slate, users are presented with helpful suggestions like:
Your usual route to work will take 24 minutes today.
The result is a mobility experience that feels less like a tool and more like an assistant.
2. Modal Comparison Cards
One of the most difficult challenges in MaaS is helping users compare transportation options without overwhelming them.
A journey might involve multiple routes, varying costs, different transfer requirements, and trade-offs between speed, comfort, and sustainability. Presenting all of this information through dense route lists or complex maps often increases decision fatigue.
Modal Comparison Cards simplify the process by presenting options in a structured and easily comparable format. Users can quickly evaluate important factors such as travel time, cost, number of transfers, and environmental impact without digging through layers of information.
The pattern works because it mirrors how people naturally make decisions. After all, they want enough clarity to choose confidently.
3. Unified Payments
One of the original promises of MaaS was convenience. Yet convenience quickly disappears when users are forced to manage separate payment systems for buses, metros, bike-sharing services, and ride-hailing providers. Unified wallets and integrated payment experiences, therefore, play a crucial role here.
Instead of treating each transportation service as an individual transaction, the platform brings everything together under a single payment ecosystem. Some MaaS platforms take this a step further by introducing subscription plans that show users how much they can save through bundled mobility services.
4. Proactive Disruption Management
Transportation systems are unpredictable. Sometimes, delays happen, routes change, and then there is the issue of the unavailability of vehicles. How the platform responds at that stage becomes a core aspect of the MaaS UX here.
Instead of simply informing users that a train is delayed, they recommend an alternative route. Instead of highlighting a problem, they provide a solution.
This pattern becomes especially valuable during multimodal journeys where users may need to switch between transportation modes. Clear handoff guidance, walking directions, pickup locations, and backup options help maintain continuity throughout the experience.
5. Behavioral Nudges
Many people understand the benefits of public transit, shared mobility, and sustainable travel. Yet long-standing habits often keep them returning to familiar choices.
Behavioral nudges help bridge that gap. Instead of simply completing a journey, the platform highlights its impact.
Users might see:
- Money saved compared to driving
- Carbon emissions reduced
- Public transit streaks achieved
- Subscription savings accumulated
These small moments of feedback make mobility benefits tangible. They transform abstract concepts like sustainability and cost efficiency into outcomes users can see and appreciate.
What India’s Leading Mobility Apps Teach Us About MaaS UX
While India doesn’t yet have many fully-fledged MaaS platforms, apps like Uber, Rapido, and inDrive provide great lessons in creating mobility experiences built on ease, cost, and real-time decision-making.
1. Uber India
Uber has transitioned from a standard premium cab service into a comprehensive ecosystem that bridges private rides with public infrastructure. Its UX focuses heavily on reducing cognitive load and managing high-density infrastructure.
Integrated Multi-Modal Transit Planning
Instead of keeping public and private transport separate, Uber’s home screen lets users buy Metro Train tickets via ONDC directly inside the app alongside local cabs, autos, and moto-taxis. In fact, the app also allows users to book intercity bus rides seamlessly.
This cross-modal synergy is the core tenet of MaaS. It reduces app-switching fatigue, mapping a user’s entire multi-leg journey in a single interface.
Image Source: UberSegmented Price/Time Controls (Wait & Save vs. Go Priority)
Uber uses a distinct tier-selection carousel that splits user intent based on urgency. Wait & Save discounts the ride for those with flexible timelines, while Go Priority targets time-sensitive travelers.
Good MaaS UX recognises that user context changes constantly. It hands financial control back to the user without complicating the screen.
"Simple Mode" for Accessibility
Uber’s dedicated Simple Mode cleanses the interface specifically for senior citizens. It features high-contrast typography, significantly expanded touch targets (larger buttons), and automated, streamlined real-time sharing with family members.
Image Source: UberHigh usability means universal access. Simplifying dense maps into text-based steps makes multi-modal transit welcoming to less tech-savvy groups.
2. Rapido
Starting as a hyper-focused two-wheeler app, Rapido has scaled aggressively into autos and cabs. Its user experience is finely tuned for hyper-local Indian commutes.
Contextual Fare Adjustments
When a user is stuck during peak traffic and cannot secure a ride, Rapido allows the rider to manually override the standard algorithm by sliding a scale to add a tip or voluntary surcharge (capped at ₹100) to incentivize drivers.
Algorithmic pricing often leaves riders stranded. Giving users a visual “override button” to directly communicate financial urgency solves real-world pain points elegantly.
Visual Vehicle-Dominant Information Architecture (IA)
Rapido’s vehicle-selection page places high-contrast, recognizable illustrative iconography of bikes and autos right upfront. This ensures that users scanning the UI under bright sunlight or in crowded streets can immediately distinguish their vehicle options.
For mobile users on the go, graphical visual hierarchy is superior to text-heavy density. It reduces cognitive friction when time is scarce.
Frictionless, Multi-Tiered “Captain” Visibility
The live-tracking interface focuses on the driver ("Captain"). It provides immediate clarity on location, eta, vehicle number, and a direct, one-tap prompt to copy the OTP or initiate a masked phone call.
Safety and pickup clarity are vital for micromobility. Reducing the distance between booking confirmation and meeting the driver keeps riders secure on active roads.
3. inDrive
inDrive rejects algorithmically driven surge models entirely. It uses a marketplace negotiation design, letting passengers and drivers directly settle on a fare.
Bidirectional Fare Bargaining Engine
The primary screen does not display a fixed total fare. Instead, it offers a smart, recommended baseline price while providing input boxes for passengers to enter their own price. The app then presents an organized list of incoming counter-offers from nearby drivers.
Image Source: LBBThis changes the user's role from a passive buyer to an active market participant. Designing this feedback loop without it feeling like a complex auction is a masterclass in clean information design.
Dual-Perspective Profile Transparency (The Bid Card)
When drivers bid on a user’s ride proposal, the app formats each offer as a distinct “Bid Card”. This card cleanly displays the counter-fare, the driver’s star rating, their lifetime trip count, and their vehicle model.
Trust is essential for peer-to-peer services. Consolidating reputation data onto a compact bid card gives users the necessary data points to make an informed choice in seconds.
Rider-Side Custom “Comment Field”
Prominently integrated into the booking layout is a specialized text field where riders can attach specific variables, such as "heavy luggage" or "traveling with a pet", which the driver sees before accepting.
By enabling users to explicitly define their physical dependencies pre-ride, the UX prevents mid-journey cancellations and minimizes communication friction.
How Onething Design Creates Better Mobility Experiences
At Onething Design, we’ve worked with mobility brands such as Nuego and Swvl, helping them create experiences that build trust and make journeys feel more seamless.
Nuego: Designing a Premium Digital Travel Experience
Nuego is India’s first premium electric intercity bus service, serving travelers who expect a more comfortable and technology-enabled travel experience.
A traveler planning a trip between cities experiences more than just purchasing a ticket. Users seek routes, schedules, boarding points, seat selection, journey data, and live updates.
While designing the Nuego experience, the focus was on simplifying decision-making and building confidence throughout the journey. From route discovery and booking flows to trip management and information hierarchy, every interaction was designed to help users feel informed, in control, and reassured.
Swvl: Simplifying Shared Mobility at Scale
Swvl operates in a fundamentally different mobility context. Unlike intercity travel, shared transportation requires users to make fast decisions within highly dynamic environments.
Commuters need to quickly understand routes, identify pickup points, track vehicles, and coordinate their journeys with minimal effort. The design challenge for Swvl was focused on clarity and efficiency. The interface has to assist consumers in finding relevant routes quickly, understand their travel alternatives, and navigate the booking process without needless complication. Special attention was paid to minimizing cognitive burden, enhancing information availability, and providing important mobility information at the time of need.
The Future of Mobility Needs Better Experiences
Well, to sum up, the most successful MaaS platforms are the ones that reduce uncertainty, simplify decisions, and make movement feel effortless. At Onething Design, we’ve seen this firsthand through our work in the mobility space. From helping shape digital experiences for brands like Nuego and Swvl to solving complex user journeys across industries, we've learned that great mobility design is never just about moving people from Point A to Point B. Honestly, it's about creating confidence at every step in between.
Whether you’re building a MaaS platform, a ride-hailing solution, a fleet management product, or the next generation of multimodal mobility services, the challenge of making complexity feel invisible to the people using it is central.
And that's where thoughtful UX design can make all the difference.
Ready to Rethink Mobility Through Better UX?
If you're building a MaaS platform or reimagining the future of mobility, we'd love to help.
At Onething Design, we collaborate with organizations to craft intuitive, scalable, human-centered mobility experiences that demystify routes, foster trust, and accelerate adoption.
Because great mobility is about helping people move through the world with less friction, less uncertainty, and a little more ease.
Let's create mobility experiences people actually enjoy using.