Honolulu DTS Audio Briefing — 6 minutes

ANALYST Here's a Honolulu rider, in an app review of the legacy DaBus Two app, from twenty twenty-five. "I'll check the app and behold! Not working. No times or routes at all being shown. Now that's a dilemma. I'm stuck waiting there and hoping the bus comes."

HOST Stuck waiting there. That's not a complaint about a feature. That's a rider giving up on the information entirely.

ANALYST And it isn't only Honolulu's story. We studied sixty U.S. transit agencies, and roughly three in every four show the same pattern: riders losing trust in real-time arrivals. This episode is about what the review found here.

HOST This is edition two of a sixty-agency review of digital rider experience in U.S. transit. Let's get into it.

HOST Come back to that quote. What makes it more than an ordinary bad review?

ANALYST It's the language of a rider at the stop who has already committed to the trip. They opened the app, and it had nothing to say. The review keeps seeing three kinds of real-time trust friction: information that's wrong, information that misleads, and information that's simply absent. Honolulu's documented pattern sits in the third category. The blank screen. And the agency has already given its architectural answer. The legacy DaBus Two app was retired in April twenty twenty-six and replaced by the Transit app partnership.

HOST Did the review hear this kind of language anywhere else?

ANALYST Across the cluster. A Cleveland R-T-A rider: "Delays are bad, but the poor passenger information, ghost trains, no service announcements, makes it even worse."

ANALYST And a SEPTA rider, in an app store review: "The map function for bus is not usable. Favorites delete on every update."

ANALYST Here's the point the booklet lands on. That kind of language is durable. It outlives the technical fix that should make it unnecessary. Retiring the old app removes the blank screen. It doesn't, on its own, remove "stuck waiting there" from how riders talk about the service.

HOST Beyond the quote, what did the review observe about Honolulu D-T-S?

ANALYST First, Honolulu sits inside the cohort's largest friction pattern. Three of every four agencies show documented real-time trust friction, and Honolulu is one of the most actively transitioning agencies in the cohort, with an architectural response already in motion as the rider surface moves to Transit. The twenty twenty-five Audit also named multi-language gaps on the Skyline digital surface. The data is moving, and the rider's sense of whether to rely on the surface lags the move.

ANALYST Second, thirty-five of the sixty are in an active service-change window, and Honolulu has two change windows on the same calendar. Skyline Segment Two opened in October twenty twenty-five, and the DaBus Two to Transit migration landed in April twenty twenty-six. Public communication of service changes and public measurement of rider response are running on different timelines.

HOST Where does that put the agency overall?

ANALYST On the review's maturity arc, Honolulu D-T-S is at the Integrated tier. Only eight of the sixty agencies are there. And zero agencies have reached the top tier, called Leading. Across the cohort, roughly eighty percent of agencies still have riders navigating two or more separate apps. Nobody has closed the gap between accurate underlying data and the rider-facing trust that data is supposed to produce, and that horizon is exactly the question this study is most interested in.

HOST Has any agency treated that trust gap as its own project?

ANALYST One in the review has: New Jersey Transit. A twenty-nine day study found seventy-three percent of riders planning trips during active service advisories didn't know those advisories existed. And here's the part that matters. The data was accurate, and the alerts were live. The failure was at the moment of decision.

HOST So what did they do?

ANALYST One question. The trip planner asks it only when a rider's searched route has an active advisory: "Did you know there is a travel advisory for your trip?" The technical surface is one tag in the page header. Everything else runs server-side, and it scales automatically during disruptions.

HOST And the result?

ANALYST Seven in ten trip planners the agent reaches discover an alert they didn't know existed. In the first weeks it guided tens of thousands of riders to alerts they would have missed. And modeled at the floor of measurable value, the conservative case cleared the program cost inside the pilot window.

HOST So what happens next?

ANALYST The review used open record only. Strategic plans, board minutes, app store reviews, public rider forums. No interviews. That's the next step. This fall, Pulse Insights publishes the first cross-agency report on rider digital experience in U.S. transit, and Honolulu D-T-S is on the shortlist for the structured conversations behind it. Thirty minutes, built around the three observations in the booklet. Every observation gets sharper when an agency's own people sit down to react to it. Participating agencies get the report ahead of public release, plus a deeper readout on what the review found here.

HOST And if the person listening isn't the right person?

ANALYST They almost certainly know who is. Everything cited today is in the Honolulu D-T-S booklet.

HOST Thanks for riding with us.