This post documents a user’s detailed experience with the Dart ride‑hailing app in Brunei over February 16-18, 2026, highlighting repeated app failures, manual WhatsApp interventions and long dispatch delays (60-83 minutes). While general feedback about Dart’s app reliability exists online, this account is unique in its timeline, narrative and personal context. The post illustrates gaps between the platform’s “on-demand” promise and actual service performance, emphasizing time loss, predictability issues and the erosion of user trust.
Disclaimer This narrative reflects one user’s specific experience and observations. Although there are public reports of app instability and service delays with Dart, this account is original and not copied from any existing online content. It does not represent Dart or its staff and interpretations of the experience are based solely on the author’s perspective.
When “On-Demand” Isn’t Quite On Time 🚗⏳
A reflection on reliability, expectations, and two very long afternoons.
I’ve been a Dart rider since their early days in 2016, back when the service had only 10 drivers navigating Brunei. Back then, rides were simple, personal and predictably a wait. Fast forward to February 2026, despite a much larger fleet and expanded platform, repeated app failures and long dispatch waits remind me that scale doesn’t always guarantee consistency.
Between February 16-18, 2026, I experienced two similar booking delays using Dart in the mid-afternoon window (around 3:00-4:30 PM).
Once is an anomaly.
Twice within 48 hours - at roughly the same time slot - suggests something more structural.
📍 What Happened
February 16, 2026
🕒 3:00 PM - Began booking attempts via the app
🕒 3:54 PM - Switched to WhatsApp after repeated failures
🕓 4:14 PM - Asked to wait 16–30 more minutes
🕓 4:10 PM - Realised my 4:30 PM appointment was no longer realistic
🕓 4:23 PM - Driver finally secured
Total time: 83 minutes from first attempt to dispatch.
February 18, 2026
🕒 3:00 PM - Began booking
🕒 3:25 PM - Sent manual pickup details for 3:45 PM
🕒 3:50 PM - No update until I prompted support
Different day. Same rhythm.
Two incidents within the same peak window point more toward capacity strain or system instability than coincidence.
👤 The Who
A long-time rider navigating a system that has grown immensely over 10 years.
Support staff who were polite and professional.
Drivers likely stretched during peak-hour demand.
This isn’t about individuals.
It’s about system reliability.
🛠 How the Process Shifted
When the app didn’t function reliably, the fallback became manual booking via WhatsApp.
That meant:
- Reconfirming payment details
- Verifying email addresses
- Waiting for driver availability
- Prompting for updates
Even with existing Dart credits, the flow was not seamless.
It felt like ordering through a “one-click” checkout… only to be handed a clipboard midway through. 📝😅
Workarounds are fine when rare.
They’re concerning when routine.
📊 The Expectation Gap
Ride-hailing operates on immediacy.
Typical expectation: 5-15 minutes dispatch.
Observed experience: 60-83 minutes.
An 83-minute dispatch window represents a several-hundred-percent deviation from standard on-demand norms.
Politeness was present.
Predictability was not.
“Waiting for driver availability” is understandable.
Not knowing whether that wait is five minutes or fifty - and having to ask each time - is where friction accumulates.
Silence stretches longer than delay.
🌍 Why It Matters Beyond One User
For some, ride-hailing is convenience.
For others, it’s essential infrastructure.
Students heading home.
Medical appointments.
Work commitments.
Passengers without alternative transport.
When reliability dips, users begin building contingency buffers into their schedules.
Once people start allocating an extra hour “just in case,” the service has shifted from convenience to risk management.
That shift is subtle - but significant.
🎭 A Brief Moment of Irony
There’s something uniquely humbling about being told at 4:14 PM to wait another 16–30 minutes… when at 4:10 PM you’ve already recalculated your entire afternoon.
Time travel would have helped.
Unfortunately, that feature hasn’t been rolled out yet. ⏳🚀
🧭 The Larger Reflection
If manual chat becomes the primary pathway because the app struggles, the platform quietly changes form. It becomes less “on-demand mobility” and more “managed transport queue.”
That distinction matters.
Convenience builds adoption.
Predictability builds trust.
And trust is harder to rebuild than to maintain.
Dart fills an important transport gap. When it works, it works well.
The hope is simple: stabilise the app, strengthen peak-hour capacity and reduce the need for manual intervention.
Because reliability is invisible when it functions -
and unforgettable when it doesn’t. 🚗
No comments:
Post a Comment